… with highest memory available, and memory is what really really matters. High-Memory Quadruple Extra Large Instance 68.4 GB of memory 26 EC2…” method reduces the impact of traditional InnoDB log flushing, which can cause downward spikes in performance. Other then that, I have also… read performance to improve, but they have an impact on the write performance. Well most of the apps rely on read performance and…
Post: Index Condition Pushdown in MySQL 5.6 and MariaDB 5.5 and its performance impact
March 12, 2012 By 12 Comments
I have been working with Peter in preparation for the talk comparing the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. We are taking a look at and benchmarking optimizer enhancements one by one. So in the same way this blog post is aimed at a new optimizer enhancement Index Condition …
Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5
April 4, 2012 By 2 Comments
… performed on table2. Of course this could mean a lot of random lookups in case the dataset does not fit into memory… values by PK column and then performing the lookup, and then there are other possibilities like InnoDB doing read_ahead by noticing… when the workload fits entirely in memory. For the purpose of benchmarking in-memory workload, the InnoDB buffer pool size is set to…
Post: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5
March 21, 2012 By 10 Comments
… when the workload fits entirely in memory. For the purpose of benchmarking in-memory workload, the InnoDB buffer pool size is set to… these lookups are performed in a single call to the storage engine and the counters Handler_read_key and Innodb_rows_read… in the buffer. But there is no performance improvement when the workload is in-memory, in fact MRR adds extra sorting overhead…
Post: InnoDB Flushing: a lot of memory and slow disk
March 31, 2011 By 57 Comments
… performs changes in memory at a faster rate than it can write to disks. Eventually it gets into an “async” state, where InnoDB… InnoDB will flush, and P is our page. So, as a result of how it works, instead of performing 1 random write, InnoDB will perform 8 random writes. I do not have a…
Post: Benchmarks of new innodb_flush_neighbor_pages
January 17, 2012 By 6 Comments
… are dirty. To illustrate, say we have an area of memory like this: …D…D…D….P….D….D…D….D… InnoDB will flush, and P is our page. So, as the result of how it works, instead of performing 1 random write, InnoDB will perform 8 random writes. This is quite far from…
Post: Real-Life Use Case for "Barracuda" InnoDB File Format
April 23, 2008 By 11 Comments
… fact that with DYNAMIC row format InnoDB was able to keep an entire PRIMARY index in memory (TEXT and BLOB fields are… key (from 1-20 sec before the conversion) These interesting performance results obviously come from the fact that in addition to… trying to compress 16kb pages down to 8kb) new innodb plugin performs TEXT/BLOB/VARCHAR fields compression off-page so every large…
Post: Heikki Tuuri answers to Innodb questions, Part II
November 4, 2007 By 13 Comments
… amount of RAM from 8Gig to 16Gig help the write performance of Innodb on Solaris? HT: Yes, if your ‘write working set… while googling.“What is the good way to split memory between INNODB buffers and OS?†Of course this depends on… brands. Q37: We have a fairly large Innodb table (150GB) that is showing poor performance for full table scans. using O_DIRECT…
Post: Choosing innodb_buffer_pool_size
November 3, 2007 By 38 Comments
My last post about Innodb Performance Optimization got a lot of comments choosing proper innodb_buffer_pool_size and indeed I oversimplified things… write a bit better description. Innodb Buffer Pool is by far the most important option for Innodb Performance and it must be set… be allocated. There are also things like innodb additional memory pool (which can grow more than memory you allocated for it, especially in…
Post: Different flavors of InnoDB flushing
January 13, 2011 By 9 Comments
…. In this case, InnoDB has to flush some data to be able to perform the read. For this, InnoDB uses the LRU list… bound, then InnoDB and MySQL settings (mentioned above) do not matter a lot, and performance is mostly defined by available memory and the I/O subsystem. Also, it seems MySQL 5.1 with the InnoDB-plugin…
