May 25, 2012

Post: MySQL 4 to MySQL 5 Upgrade performance regressions

MySQL handled this problem. While working for MySQL we spotted this problem early in MySQLlarge amount of log writes and fsyncs per second which matches your hard drive capacity

Post: High-Performance Click Analysis with MySQL

large amounts of space.  Choose primary keys very carefully, especially with InnoDB tables — don’t use GUIDs.  Which brings me toof data processing in MySQL, you’re going to end up heavily I/O bound.  Listen to any of the talks at past MySQLof ways to handle

Post: Is disk Everything for MySQL Performance ?

to show search results which does not require too much IO capacity or high in memory fit. For large number ofamount of disk at your disposal and if you have BBU most likely data

Post: Scaling: Consider both Size and Load

amount of data each). Doubling traffic for system of such type means handling twice amount of transactions on the twice amount of data. Increasing amount of data

Post: Innodb Fuzzy checkpointing woes

of these are benchmarks)    just after very large amount ofto say this device can handle 1000 requests per second and the best would be toto perform at their full capacity.   One more thing to