… with highest memory available, and memory is what really really matters. High-Memory Quadruple Extra Large Instance 68.4 GB of memory 26 EC2… used: ## InnoDB options innodb_buffer_pool_size = 55G innodb_log_file_size = 1G innodb_log_files_in_group = 4 innodb_buffer_pool_instances = 4 innodb_adaptive…
Post: Troubleshooting MySQL Memory Usage
March 21, 2012 By 3 Comments
… in set (0.00 sec) Innodb Memory Usage Finally it is often helpful to check how much memory Innodb has allocated. In fact this…. Run SHOW ENGINE INNODB STATUS and look for memory information block, which can use like this: ———————- BUFFER POOL AND MEMORY ———————- Total memory allocated 132183490560…
Comment: Troubleshooting MySQL Memory Usage
March 22, 2012 By 3 Comments
I think it’s worth to say here that the InnoDB team has already made some effort to address memory usage problems: http://blogs.innodb.com/wp/2011/12/improving-innodb-memory-usage-continued/ . Results seem very promising, and also maybe these fixes will allow more precise memory usage monitoring.
Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5
April 4, 2012 By 2 Comments
… when the workload fits entirely in memory. For the purpose of benchmarking in-memory workload, the InnoDB buffer pool size is set to… 2.2G Innodb_data_reads 329115 355323 143808 335526 16164 15506 Innodb_pages_read 329115 355323 143808 358308 144798 144881 Innodb_rows_read… two other most important numbers are values for Innodb_buffer_pool_reads and Innodb_data_read. We can see that with appropriately…
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… workload fits entirely in memory, because there is no extra cost for memory access at random locations versus memory access at sequential locations….89G 1.53G Innodb_data_reads 120552 123872 100551 103011 77213 Innodb_pages_read 120548 123868 100551 123592 100566 Innodb_rows_read 799239…
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 …
Comment: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5
March 23, 2012 By 10 Comments
… it would be to use the same random dives trick Innodb uses – You can do 100 partial random dives in the… short of reading it. This would get you approximate in memory fit for each index and it can be refreshed every… cases as frequently you would have only some portion in memory, but it is the portion which is queried the most…
Post: Percona Server 5.5.21-25.1 released!
March 29, 2012 By 8 Comments
…: Fixed a memory corruption regression introduced in 5.5.18-23.0. Bug fixed #915814 (Alexey Kopytov). Fixed InnoDB compilation warnings on…
Post: InnoDB memory usage
May 30, 2006 By 6 Comments
… memory allocation at startup. Some important constants: NBLOCKS=count of block in innodb_buffer_pool = innodb_buffer_pool_size / 16384 OS_THREADS= if (innodb… and memory for locking system, size=5 * 4 * NBLOCKS So the final formula for innodb: innodb_buffer_pool_size + innodb_log_buffer_size + innodb_additional…
Post: InnoDB memory allocation, ulimit, and OpenSUSE
August 23, 2010 By 7 Comments
…_malloc_low() in ut/ut0mem.c inside InnoDB source code. InnoDB wraps the majority of its memory allocations in ut_malloc_low(), so…. Apparenly OpenSUSE defaults are set in proportion to physical memory to keep the memory-hungry applications from taking the system down. On… physical memory, 2 GB swap it decided to set the virtual memory ulimit (-v) to 77.27 GB, and the physical memory (-m…
