Author Archives: zardosht

A Case for Write Optimizations in MySQL

Posted on by zardosht

As a storage engine developer, I am excited for MySQL 5.6. Looking at http://dev.mysql.com/tech-resources/articles/whats-new-in-mysql-5.6.html, there has been plenty of work done to improve the performance of reads in MySQL for all storage engines (provided they take advantage of…

1 Comment

Understanding Indexing – NY Effective MySQL...

Posted on by zardosht

At next week’s NY Effective MySQL Meetup, I will give a talk: “Understanding Indexing: Three rules on making indexes around queries to provide good performance.” The meetup is 7 pm Tuesday, October 11th, and will be held at…

Leave a comment

Indexing: The Director’s Cut

Posted on by zardosht

Thanks again to Erin O’Neill and Mike Tougeron for having me at the SF MySQL Meetup last month for the talk on “Understanding Indexing.” The crowd was very interactive, and I appreciated that over 100 people signed up for…

1 Comment

Understanding Indexing – SF MySQL Meetup

Posted on by zardosht

At this week’s SF MySQL Meetup, I will give a talk: “Understanding Indexing: Three rules on making indexes around queries to provide good performance.” The meetup is 7 pm tomorrow (Wednesday, 6/22), and will be held at CBS Interactive…

1 Comment

Effective MySQL, a New York City Meetup

Posted on by zardosht

Kudos to Ronald Bradford for creating a new MySQL meetup group in New York city and giving MySQL related talks. The next one is tonight, titled “MySQL Idiosyncrasies That Bite”. Information on it can be found at http://ny.effectivemysql.com/events/16884850/.
We’ll…

Leave a comment

Understanding Indexing – MySQL Meetup

Posted on by zardosht

Yesterday, at the Boston MySQL Meetup, I gave a talk on indexing. It is posted here (also goo.gl/S2LBe).
In short, indexes are used to improve query performance. As a result, good indexes are designed around queries that…

Leave a comment

Scenarios where TokuDB’s Loader is Used

Posted on by zardosht

TokuDB’s loader uses the available multicore computing resources of the machine to presort and insert the data. In the last couple of posts (here and here), Rich and Dave presented performance results of TokuDB’s loader.…

Leave a comment

On “Replace Into”, “Insert...

Posted on by zardosht

In posts on June 30 and July 6, I explained how implementing the commands “replace into” and “insert ignore” with TokuDB’s fractal trees data structures can be two orders of magnitude faster than…

Leave a comment

On “Replace Into”, “Insert...

Posted on by zardosht

In posts on June 30 and July 6, I explained how implementing the commands “replace into” and “insert ignore” with TokuDB’s fractal trees data structures can be two orders of magnitude faster than…

Leave a comment

Why “insert … on duplicate key...

Posted on by zardosht

In my post on June 18th, I explained why the semantics of normal ad-hoc insertions with a primary key are expensive because they require disk seeks on large data sets. I previously explained why it would be better

6 Comments