Monthly Archives - January 2011

MySQL & Friends Meetup @ FOSDEM

Kris Buytaert organized a MySQL Meetup at FOSDEM last year, and because of the success we’ll be doing it again this year, in the same restaurant: Sogno d’Italia.
Everybody is invited to come to the dinner. Just register on http://mysqlandfriendsfosdem2011.eventbrite.com/ so we have an idea how many reservations we should make. The maximum capacity is about 40 people.
We’ll plan to […]

Read more

Partitioning, Free Lunches, & Indexing, Part 2

Review
In part one, I presented a very brief and particular view of partitioning. I covered what partitioning is, with hardly a mention of why one would use partitioning. In this post, I’ll talk about a few use cases often cited as justification for using partitions.
Lots of disks → Lots of partitioning of tables
One […]

Read more

Modeling InnoDB Scalability on Multi-Core Servers

Mat Keep’s blog post on InnoDB-vs-MyISAM benchmarks that Oracle recently published prompted me to do some mathematical modeling of InnoDB’s scalability as the number of cores in the server increases. Vadim runs lots of benchmarks that measure what happens under increasing concurrency while holding the hardware constant, but not as many with varying […]

Read more

Percona Live: Venu Anuganti; early bird registration expires tomorrow

Today we are announcing Venu Anuganti as a guest speaker to Percona Live: San Francisco.
Venu works as a Data architect, evaluating and implementing high performance SQL/NoSQL data store solutions for large scale OLTP and OLAP infrastructure; and previously worked as a database kernel engineer at companies like SolidDB, MySQL, ANTs Data […]

Read more

Partitioning, Free Lunches, and Indexing

Why partition?
Partitioning is a commonly touted method for achieving performance in MySQL and other databases. (See here, here, here and many other examples.) I started wondering where the performance from partitions comes from, and I’ve summarized some of my thoughts here.
But first, what is partitioning? (I’ve taken the examples […]

Read more

Different flavors of InnoDB flushing

In my recent benchmarks, such as this one about the Virident TachIon card, I used different values for innodb_buffer_pool_size, like 13GB, 52GB, and 144GB, for testing the tpcc-mysql database with size 100G. This was needed in order to test different memory/dataset size ratios. But why is it important, and how does it affect how InnoDB […]

Read more