Home |  MySQL Buzz |  FAQ |  Feeds |  Submit your blog feed |  Feedback |  Archive |  Aggregate feed RSS 2.0 English Deutsch Español Français Italiano 日本語 Русский Português 中文
Previous 30 Newer Entries Showing entries 31 to 46

Displaying posts with tag: sysbench (reset)

NILFS – may be not yet
+1 Vote Up -0Vote Down

Inspired by NILFS: A File System to Make SSDs Scream and some customers asked if they should try NILFS on their SSD disks I decided to run quick tests to see how it performs.

Installation on our Ubuntu 8.10 with SSD disk (Intel X25-E, 32GB) was pretty plain and I got partition with NILFS without problem. After that I run script for sysbench fileio:

PLAIN TEXT CODE:
  • for size in 256M 16G; do
  •    for mode in seqwr seqrd rndrd rndwr rndrw; do
  •       ./sysbench --test=fileio --file-num=1 --file-total-size=$size prepare
  •       for threads in 1 4 8; do
  •          echo PARAMS $size $mode $threads>
  •   [Read more...]
    Setting up sysbench with MySQL & Drizzle
    +2 Vote Up -0Vote Down

    Sysbench is a open source product that enables you to perform various system benchmarks including databases. Drizzles performs regression testing of every trunk revision with a branched version of sysbench within Drizzle Automation.

    A pending branch https://code.launchpad.net/~elambert/sysbench/trunk_drizzle_merge by Eric Lambert now enables side by side testing with MySQL and Drizzle. On a system running MySQL and Drizzle I was able install this sysbench branch with the following commands.

    cd bzr
    bzr branch lp:~elambert/sysbench/trunk_drizzle_merge
    cd trunk_drizzle_merge/
    ./autogen.sh
    ./configure
    make
    sudo make install
    

    Running the default lua tests

      [Read more...]
    configure: error: mysql_config executable not found
    +0 Vote Up -0Vote Down

    If your compiling a product that includes a dependency of MySQL, you can easily get the error

    configure: error: mysql_config executable not found
    

    I generally don’t see this problem, because I use MySQL binary tar files, however if you use MySQL packages, such as Ubuntu, you can easily miss the required dependency.

    My currently installed MySQL packages on this Ubuntu machine are:

    $ sudo dpkg -l | grep mysql
    ii  libdbd-mysql                               0.8.2-1-4.1                               MySQL database server driver for libdbi
    ii  libdbd-mysql-perl                          4.008-1                                   A Perl5 database interface to the MySQL data
    ii  libmysqlclient15off                        5.1.30really5.0.75-0ubuntu10.2            MySQL database client library
    ii  libmysqlclient16
      [Read more...]
    MySQL 5.4 Scaling on Nehalem with Sysbench
    Employee +1 Vote Up -0Vote Down
    As a final followup to my MySQL 5.4 Scalability on 64-way CMT Servers blog, I'm posting MySQL 5.4 Sysbench results on a Sun Fire X4270 platform using the Intel x86 Nehalem chip (2 sockets/8 cores/16 threads). All CPUs were turned on during the runs. The my.cnf was the same as described in the previous blog.

    The Sysbench version used was 0.4.12, and the read-only runs were invoked with the following command:

    sysbench --max-time=300 --max-requests=0 --test=oltp --oltp-dist-type=special --oltp-table-size=10000000 \
       --oltp-read-only=on --num-threads=[NO_THREADS] run
    

    The "oltp-read-only=on" parameter was omitted for the read-write tests. The my.cnf file listed in my previous blog was also used unchanged for these tests.

    Here are the results graphically running on Linux.

      [Read more...]
    MySQL 5.4 Sysbench Scalability on 64-way CMT Servers
    Employee +1 Vote Up -0Vote Down
    As a followup to my MySQL 5.4 Scalability on 64-way CMT Servers blog, I'm posting MySQL 5.4 Sysbench results on the same platform. The tests were carried out using the same basic approach (i.e. turning off entire cores at a time) - see my previous blog for more details.

    The Sysbench version used was 0.4.8, and the read-only runs were invoked with the following command:

    sysbench --max-time=300 --max-requests=0 --test=oltp --oltp-dist-type=special --oltp-table-size=10000000 \
       --oltp-read-only=on --num-threads=[NO_THREADS] run
    
    The "oltp-read-only=on" parameter was omitted for the read-write tests. The my.cnf file listed in my previous blog was also used unchanged for these tests.

    Here is the data presented graphically. Note that the number of vCPUs is the same as the number of active

      [Read more...]
    MySQL 5.4 Scaling on Nehalem with Sysbench
    Employee +0 Vote Up -0Vote Down
    As a final followup to my MySQL 5.4 Scalability on 64-way CMT Servers blog, I'm posting MySQL 5.4 Sysbench results on a Sun Fire X4270 platform using the Intel x86 Nehalem chip (2 sockets/8 cores/16 threads). All CPUs were turned on during the runs. The my.cnf was the same as described in the previous blog.

    The Sysbench version used was 0.4.12, and the read-only runs were invoked with the following command:

    sysbench --max-time=300 --max-requests=0 --test=oltp --oltp-dist-type=special --oltp-table-size=10000000 \\
       --oltp-read-only=on --num-threads=[NO_THREADS] run
    

    The "oltp-read-only=on" parameter was omitted for the read-write tests. The my.cnf file listed in my previous blog was also used unchanged for these tests.

    Here are the results graphically running on Linux.

      [Read more...]
    MySQL 5.4 Scaling on Nehalem with Sysbench
    Employee +0 Vote Up -0Vote Down
    As a final followup to my MySQL 5.4 Scalability on 64-way CMT Servers blog, I'm posting MySQL 5.4 Sysbench results on a Sun Fire X4270 platform using the Intel x86 Nehalem chip (2 sockets/8 cores/16 threads). All CPUs were turned on during the runs. The my.cnf was the same as described in the previous blog.

    The Sysbench version used was 0.4.12, and the read-only runs were invoked with the following command:

    sysbench --max-time=300 --max-requests=0 --test=oltp --oltp-dist-type=special --oltp-table-size=10000000 \\
       --oltp-read-only=on --num-threads=[NO_THREADS] run
    

    The "oltp-read-only=on" parameter was omitted for the read-write tests. The my.cnf file listed in my previous blog was also used unchanged for these tests.

    Here are the results graphically running on Linux.

      [Read more...]
    MySQL 5.4 Sysbench Scalability on 64-way CMT Servers
    Employee +0 Vote Up -0Vote Down
    As a followup to my MySQL 5.4 Scalability on 64-way CMT Servers blog, I'm posting MySQL 5.4 Sysbench results on the same platform. The tests were carried out using the same basic approach (i.e. turning off entire cores at a time) - see my previous blog for more details.

    The Sysbench version used was 0.4.8, and the read-only runs were invoked with the following command:

    sysbench --max-time=300 --max-requests=0 --test=oltp --oltp-dist-type=special --oltp-table-size=10000000 \\
       --oltp-read-only=on --num-threads=[NO_THREADS] run
    
    The "oltp-read-only=on" parameter was omitted for the read-write tests. The my.cnf file listed in my previous blog was also used unchanged for these tests.

    Here is the data presented graphically. Note that the number of vCPUs is the same as the number of

      [Read more...]
    MySQL 5.4 Sysbench Scalability on 64-way CMT Servers
    Employee +0 Vote Up -0Vote Down
    As a followup to my MySQL 5.4 Scalability on 64-way CMT Servers blog, I'm posting MySQL 5.4 Sysbench results on the same platform. The tests were carried out using the same basic approach (i.e. turning off entire cores at a time) - see my previous blog for more details.

    The Sysbench version used was 0.4.8, and the read-only runs were invoked with the following command:

    sysbench --max-time=300 --max-requests=0 --test=oltp --oltp-dist-type=special --oltp-table-size=10000000 \\
       --oltp-read-only=on --num-threads=[NO_THREADS] run
    
    The "oltp-read-only=on" parameter was omitted for the read-write tests. The my.cnf file listed in my previous blog was also used unchanged for these tests.

    Here is the data presented graphically. Note that the number of vCPUs is the same as the number of

      [Read more...]
    Scalability and Stability for SysBench on Solaris
    Employee +0 Vote Up -0Vote Down

    My mind is playing "Suffering Succotash..."

    I have been working on MySQL performance for a while now, and the team I am in have discovered that SysBench could do with a couple of tweaks for Solaris.

    Sidebar - sysbench is a simple "OLTP" benchmark which can test multiple databases, including MySQL. Find out all about it here , but go to the download page to get the latest version.

    To simulate multiple users sending requests to a database, sysbench uses multiple threads. This leads to two issues we have identified with SysBench on Solaris, namely:

    • The implementation of random() is explicitly identified as unsafe in multi-threaded applications on Solaris. My team has found

      [Read more...]
    Scalability and Stability for SysBench on Solaris
    Employee +0 Vote Up -0Vote Down

    My mind is playing "Suffering Succotash..."

    I have been working on MySQL performance for a while now, and the team I am in have discovered that SysBench could do with a couple of tweaks for Solaris.

    Sidebar - sysbench is a simple "OLTP" benchmark which can test multiple databases, including MySQL. Find out all about it here , but go to the download page to get the latest version.

    To simulate multiple users sending requests to a database, sysbench uses multiple threads. This leads to two issues we have identified with SysBench on Solaris, namely:

    • The implementation of random() is explicitly identified as unsafe in multi-threaded applications on Solaris. My team has found

      [Read more...]
    Scalability and Stability for SysBench on Solaris
    Employee +0 Vote Up -0Vote Down

    My mind is playing "Suffering Succotash..."

    I have been working on MySQL performance for a while now, and the team I am in have discovered that SysBench could do with a couple of tweaks for Solaris.

    Sidebar - sysbench is a simple "OLTP" benchmark which can test multiple databases, including MySQL. Find out all about it here , but go to the download page to get the latest version.

    To simulate multiple users sending requests to a database, sysbench uses multiple threads. This leads to two issues we have identified with SysBench on Solaris, namely:

    • The implementation of random() is explicitly identified as unsafe in multi-threaded applications on Solaris. My team has

      [Read more...]
    So, what's the bottleneck?
    +0 Vote Up -0Vote Down

    I recently released some RAID testing I did using the sysbench testing framework.  In light of the recent attention paid to multi-core CPU scalability, I have been working on some related tests trying to identify sources of contention using that same set of tests.
    After effectively turning off every single innodb safety setting (like flush_log_at_trx_commit, checksums, doublewrite, etc.), and not seeing any real performance increase, I started to wonder what was going on.  
    Surely my test client server wasn't the problem, it had plenty of idle CPU according to top, right?  Wrong.
    I've been able to drive more QPS to my mysql test servers by starting up parallel sysbench tests from multiple test servers, but using (more or less) the same number of total test threads.  

    read more

    So, what's the bottleneck?
    +0 Vote Up -0Vote Down

    I recently released some RAID testing I did using the sysbench testing framework.  In light of the recent attention paid to multi-core CPU scalability, I have been working on some related tests trying to identify sources of contention using that same set of tests.
    After effectively turning off every single innodb safety setting (like flush_log_at_trx_commit, checksums, doublewrite, etc.), and not seeing any real performance increase, I started to wonder what was going on.  
    Surely my test client server wasn't the problem, it had plenty of idle CPU according to top, right?  Wrong.
    I've been able to drive more QPS to my mysql test servers by starting up parallel sysbench tests from multiple test servers, but using (more or less) the same number of total test threads.  

    -->

    read more

    mysql proxy 0.6.1 performance tests
    +0 Vote Up -0Vote Down

    The mysql proxy project has tremendous potential to make mysql administration and usage easier. I decided to throw some load at it to get a feel for how stable and performant it is.

    On EC2, I set up 6 “small” images in an example proxy setup:

    - One client machine to run sysbench
    - One machine to act as a mysql proxy machine, running 0.6.1 (FC4 binary)
    - Four identical database servers, running mysql 5.0.45

    The database configuration was largely default, with InnoDB configured for 64MB buffer pool (just enough to ensure the sysbench table was entirely in memory), 512MB log files, and 1024 max connections.

    mysql-proxy was run with the following command:

    mysql-proxy –proxy-backend-addresses=ip-10-251-66-63.ec2.internal:3306 –proxy-backend-addresses=ip-10-251-71-21.ec2.internal:3306











      [Read more...]
    sysbench - Linux Test Bench
    +0 Vote Up -0Vote Down

    sysbench - Linux test bench. Easy as pie to test CPU, memory, threads, mysql, and disk performance.

    Full description is available here: http://sysbench.sourceforge.net/docs/

    install mysql, mysql-devel
    wget http://superb-west.dl.sourceforge.net/sourceforge/sysbench/sysbench-0.4.8.tar.gz
    tar xvzf sysbench*gz
    cd sysbench*
    ./configure && make install

    mysql tests

    This will run 10 separate consecutive mysql tests using an InnoDB table type, each with 100 mysql threads, doing a total of 1000 various SQL operations per test. Then it will print the total time they took to finish:

    sysbench --test=oltp --mysql-user=USER --mysql-password=PASS --mysql-db=test \\
      --mysql-host='HOST' --mysql-table-engine=innodb prepare
     
    time perl -e
      [Read more...]
    Previous 30 Newer Entries Showing entries 31 to 46

    Planet MySQL © 1995, 2014, Oracle Corporation and/or its affiliates   Legal Policies | Your Privacy Rights | Terms of Use

    Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.