… and ran few CPU-bound tasks there. The goal of benchmarks was investigation of InnoDB-plugin and XtraDB scalability in CPU-bound load. CPU specification: processor : 23 vendor_id : GenuineIntel cpu family : 6 model : 29…
Post: XtraDB in CPU-bound benchmark
December 18, 2008 By Leave a Comment
… run for CPU Bound,or it would be more correctly to say in-cache benchmark, because there is a lot of CPU remains idle. This run is exactly the same as Disk Bound but with innodb_buffer_pool_size=8G… at CPU usage graph. As you can see they are very different for XtraDB and Innodb storage engines. Innodb has generally higher CPU usage…
Post: Are you designing IO bound or CPU bound application ?
December 20, 2006 By 10 Comments
… MySQL Consulting work or even more frequently. IO Bound workload is quite different from CPU bound one, which happens when your working set… application back to speed. The cases when going from CPU bound to IO bound hits the most is there a lot of rows… ORDER BY .. LIMIT. For IO bound applications Clustering (data locality) also becomes very important – if Innodb tables are used having simply auto…
Post: InnoDB thread concurrency
June 5, 2006 By 4 Comments
…_innodb–; ENTER; } retry: if (entered_thread < innodb_thread_concurrency) { entered_threads++; thread->n_tickets_to_enter_innodb = innodb_concurrency_tickets; ENTER; } if (innodb_… each CPU and Disk resource. For Disk IO bound workload you could only account number of disks and for CPU bound only …
Post: InnoDB compression woes
May 20, 2011 By 14 Comments
… difference. As workload is clear read-only CPU bound, let’s check CPU stats: regular tables: —–cpu—— us sy id wa st 1 0… number. With compressed tables CPU utilization is 7%. Obviously we have some mutex serialization problem. Analyzing SHOW INNODB STATUS (SEMAPHORES) for workload…
Post: XtraDB benchmarks - 1.5X gain in IO-bound load
December 18, 2008 By 30 Comments
… is CPU bound. I compared MySQL 5.1.30 trees – MySQL 5.1.30 with standard InnoDB, MySQL 5.1.30 with InnoDB-plugin… and innodb_flush_method=O_DIRECT to emulate IO bound load. InnoDB parameters: innodb_additional_mem_pool_size = 16M innodb_buffer_pool_size = 2G innodb_data_file_path = ibdata1:10M:autoextend innodb_file…
Post: MySQL 5.0, 5.1 and Innodb Plugin CPU Efficiency
December 3, 2008 By 15 Comments
… not only run MySQL plugin but also use new “Barracuda” Innodb format you see just 1% slow down with 2 cores… execution path. Another thing to note – if you’re using Innodb Plugin consider using new Barracuda format, though do this only… this format will not be recognized by older Innodb versions. Note: These are completely CPU bound test conditions, data fits to buffer pool…
Post: How to load large files safely into InnoDB with LOAD DATA INFILE
July 3, 2008 By 28 Comments
… machine from another, which takes about 10 or 12 hours. InnoDB is not optimized for rollbacks, it’s optimized for transactions…, col2 bigint(20) default NULL, key(col1), key(col2) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 Here’s the result of loading the… CPU time during the loads. So not very much at all. Some interesting things to note: the load was probably mostly CPU-bound…
Post: Join performance of MyISAM and Innodb
May 29, 2006 By 6 Comments
… which involved benchmarks of Join speed for MyISAM and Innodb storage engines for CPU bound workload, this is when data size is small… data is clustered together with index and generally highly optimized Innodb builds hash indexes which helps to speed up lookup by… to request next row matching index Note: This applies to CPU bound workload with all content fitting in memory. In other cases…
Post: InnoDB vs MyISAM vs Falcon benchmarks - part 1
January 8, 2007 By 117 Comments
… was a popular myth that MyISAM is faster than InnoDB in reads, as InnoDB is transactional, supports Foreign Key and has an… also use CPU bound workload in this case (no disk IO) to see how efficient storage engines are in terms of CPU usage… MyISAM / InnoDB: libexec/mysqld –no-defaults –user=root –key-buffer-size=1500M –innodb-buffer-pool-size=1500M –innodb-log-file-size=100M –innodb-thread…
