… number of context switches. These correspond to different contention situations which can be handled differently. First situation often corresponds to Innodb spending a lot… switching because Innodb is not spinning too much, thus you can consider increasing innodb_sync_spin_loops to a higher number. It is worth to…
Post: SHOW INNODB STATUS walk through
July 17, 2006 By 40 Comments
… CPUs. innodb_sync_spin_loops can be used to ballance between wasting CPU time running spin locks and doing unneeded context switches. The…. In addition to Innodb specific information, there is generic statement information which is visible in SHOW PROCESSLIST showed in SHOW INNODB STATUS, such…
Post: Maximal write througput in MySQL
February 28, 2010 By 10 Comments
… innodb_flush_log_at_trx_commit = 0 maximal tps is 36332.02 tps, which drops to 23115.04 tps as we switch to innodb_flush_log_at_trx_commit = 1. As we use RAID10 with BBU, I did not expect the drops is going to… results drops to 17451.01 tps with innodb_flush_log_at_trx_commit = 0 and to 12097.39 tps with innodb_flush_log_at…
Post: InnoDB benchmarks
January 3, 2007 By 15 Comments
… changes in InnoDB to fix scalabilty problems, so I ran benchmark to check new results and also compare overall performance of InnoDB in 5…-innodb and next startup options were used: libexec/mysqld –no-defaults –user=root –innodb-buffer-pool-size=1500M –innodb-log-file-size=100M –innodb… 10-23% for full table scan queries. I unambiguously recommend to switch to 5.0.30 – 5.0.32 release when it is…
Post: Internals of InnoDB mutexes
September 7, 2006 By 4 Comments
… switching. However we can’t run spin very long as it eats CPU resources and after some loops it is reasonable to… 95, where count of condition variables was limited, so InnoDB had to implement workaround. The same synchronization array is performance problematic, as… to protect cells. With big respect to InnoDB team they still take care of users of Windows 95 I think it is better to…
Comment: MySQL Partitioning - can save you or kill you
June 28, 2012 By 45 Comments
….php/memory For InnoDB, innodb_buffer_pool_size = 5500M might be optimal. (Plus key_buffer_size = 20M) If you switch to InnoDB, keep in mind the issues raised in http://mysql.rjweb.org/doc.php/myisam2innodb , starting with “Disk space for InnoDB is likely to be 2-3 times as much as for MyISAM…
Comment: Should you move from MyISAM to Innodb ?
October 2, 2012 By 59 Comments
Excellent discussion on the differences between InnoDB and MyISAM. It seems that the benefits far outweight the caveats though in switching to InnoDB‘s engine over MyISAM. =0)
Comment: Should you move from MyISAM to Innodb ?
January 12, 2009 By 59 Comments
We evaluated switching to InnoDB. Performance vs. MySQL was horrible, even after tuning. SELECT performance … needed to do a restore of any table in InnoDB, we would need to restore the full InnoDB database from tape, move it to another… time to do this is just unacceptable. To be real honest, I don’t know why a production shop would use InnoDB based…
Comment: MySQL Partitioning - can save you or kill you
June 28, 2012 By 45 Comments
…, Timestamp) – Unique. Using InnoDb engine as the client is very finiky about his records. Cant lose them due to a crash. Though there are nightly backups of the disk, still better to use InnoDb (though disk requirements… machine.. (Do not understand the issue.. This was another reason to switch to InnoDb) Lastly, its been decided today by senior architects that the…
Comment: MySQL Partitioning - can save you or kill you
June 28, 2012 By 45 Comments
… is possible in some applications. XtraDB shines over MyISAM and InnoDB. TokuDB may shine even with lots of indexes. INDEXes can…/sec. Dropping the secondary indexes — can insert faster. If he switches to InnoDB, it will depend, again, on the randomness of the data…. (XtraDB has a significant fix for smoothing out this operation; InnoDB periodically “stalls”.) In either engine, even without dropping the unused…
