Note that there are some explanatory texts on larger screens.

plurals
  1. POstrange mysql performance
    primarykey
    data
    text
    <p>I've been conducting some mysql performance tests and have yield very strange results. I am running a query across the following mysql versions: 5.0.91, 5.1.52, 5.1.52 with innodb-plugin, and 5.5.7.</p> <p>Here is the execution time for the query on each version:</p> <pre><code>version time ------------------------ 5.0: 95s 5.1: 122s 5.1 innodb-plugin: 159s 5.5: 127s </code></pre> <p>I am testing against same data (50M records in one table), on Windows 2003. Database is using InnoDB engine on all versions.</p> <p>I don't understand how MySQL 5.0 would be the fastest, how the innodb-plugin yields worst results than when not in use and how 5.5 is so similar to 5.1 in performance.</p> <p>Anyone run into this? Anyone have suggestions?</p> <p>Here are my.ini configs:</p> <ul> <li>query_cache_size=0</li> <li>table_cache=256</li> <li>tmp_table_size=2000M</li> <li>thread_cache_size=32</li> <li>innodb_additional_mem_pool_size=128M</li> <li>innodb_flush_log_at_trx_commit=2</li> <li>innodb_log_buffer_size=4M</li> <li>innodb_buffer_pool_size=8G</li> <li>innodb_log_file_size=256M</li> <li>innodb_thread_concurrency=32</li> </ul> <p>innodb-plugin specific:</p> <ul> <li>ignore_builtin_innodb</li> <li>plugin-load=innodb=ha_innodb_plugin.dll;innodb_trx=ha_innodb_plugin.dll;innodb_locks=ha_innodb_plugin.dll;innodb_lock_waits=ha_innodb_plugin.dll;innodb_cmp=ha_innodb_plugin.dll;innodb_cmp_reset=ha_innodb_plugin.dll;innodb_cmpmem=ha_innodb_plugin.dll;innodb_cmpmem_reset=ha_innodb_plugin.dll</li> <li>innodb_file_format=Barracuda</li> <li>innodb_io_capacity=400</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload