EmergencyEMERGENCY? Get 24/7 Help Now!

Maximal write througput in MySQL

 | February 28, 2010 |  Posted In: Benchmarks, MySQL

I recently was asked what maximal amount transactions per second we can get using MySQL and XtraDB / InnoDB storage engine if we have high-end server. Good questions, though not easy to answer, as it depends on: – durability setting ( innodb_flush_log_at_trx_commit = 0 or 1 ) ? – do we use binary logs ( […]

Read More

MySQL 5.5-m2 scalability

 | February 28, 2010 |  Posted In: MySQL

Oracle recently announcent MySQL-5.5.2-m2 milestone, and I have a predition that MySQL-5.5 will be announced as GA on MySQL UC 2010 in April. So let’s make quick on scalability characteristics we should expect from new release. I made sysbench oltp benchmarks on 10 mln rows (worth 2.5GB of data), on our Dell R900 system ( […]

Read More

Announcing General Availability of TokuDB v3.0 with ACID Support

 | February 23, 2010 |  Posted In: Tokutek, TokuView

Tokutek is pleased to announce immediate availability of TokuDB for MySQL, version 3.0. It is designed for continuous querying and analysis of large volumes of rapidly arriving and changing data, while maintaining full ACID properties. TokuDB v3.0 combines our long-standing performance advantages with ACID compliant transactional integrity: 10x-50x faster indexing for faster querying Full support […]

Read More

Missleading Innodb message on recovery

 | February 15, 2010 |  Posted In: Insight for DBAs, MySQL

As I wrote about 2 years ago the feature of Innodb to store copy of master’s position in Slave’s Innodb tablespace got broken. There is a lot of discussions at the corresponding bug report while outcome of the fix remained uncertain for me (the bug is market duplicate while the bugs it seems to be […]

Read More


 | February 11, 2010 |  Posted In: Benchmarks, MySQL

Question what is better isolation level is poping up again and again. Recently it was discussed in InnoDB : Any real performance improvement when using READ COMMITED isolation level ? and in Repeatable read versus read committed for InnoDB . Serge in his post explains why READ COMMITED is better for TPCC load, so why […]

Read More

Blob Storage in Innodb

 | February 9, 2010 |  Posted In: Insight for DBAs, MySQL

I’m running in this misconception second time in a week or so, so it is time to blog about it. How blobs are stored in Innodb ? This depends on 3 factors. Blob size; Full row size and Innodb row format. But before we look into how BLOBs are really stored lets see what misconception […]

Read More

Introducing percona-patches for 5.1

 | February 9, 2010 |  Posted In: MySQL, Percona Software

Our patches for 5.0 have attracted significant interest.  You can read about SecondLife’s experience here, as well as what Flickr had to say on their blog.  The main improvements come in both performance gains and improvements to diagnostics (such as the improvements to the slow log output, and INDEX_STATISTICS). Despite having many requests to port […]

Read More

Introducing tpce-like workload for MySQL

 | February 8, 2010 |  Posted In: Benchmarks, MySQL

We have been using tpcc-mysql benchmark for long time, and there many results published in our blog, but that’s just single workload. That’s why we are looking into different benchmarks, and one of them is TPCE. Yasufumi made some efforts to make TPCE working with MySQL, and we are making it available for public consideration. […]

Read More

Percona’s widely read Percona Data Performance blog highlights our expertise in enterprise-class software, support, consulting and managed services solutions for both MySQL® and MongoDB® across traditional and cloud-based platforms. The decades of experience represented by our consultants is found daily in numerous and relevant blog posts.

Besides specific database help, the blog also provides notices on upcoming events and webinars.
Want to get weekly updates listing the latest blog posts? Subscribe to our blog now! Submit your email address below and we’ll send you an update every Friday at 1pm ET.

No, thank you. Please do not ask me again.