May 25, 2012

Post: Why MySQL could be slow with large tables ?

… selectivity might show benefit from using indexes. In fact even MySQL optimizer currently does not take it into account. For In memory…. Here is good example. As we saw my 30mil rows (12GB) table was scanned in less than 5 minutes. Now if… large data sets. In MySQL single query runs as single thread (with exeption of MySQL Cluster) and MySQL issues IO requests one by…

Post: Choosing innodb_buffer_pool_size

… about Innodb Performance Optimization got a lot of comments choosing proper innodb…just checked on our set of boxes which use 12GB buffer pool (with very small additional pool …needs you also have MySQL needs – these include MySQL buffers – query cache, key_buffer, mysql threads, temporary tables, …

Post: Master-Master or Master with Many Slaves

… criticizes Master-Master approach, finding Master with many slaves more optimal. There is surely room for master-N-slaves systems but… to handle much more write load. Especially keeping into account MySQL replication is single thread it might be not long before… if you have 16GB boxes and say 12GB allocated to MySQL database caches you can get 12GB effective cache on the master-N…

Post: How innodb_open_files affects performance

… appropriate .ibd file may be open or closed. Furthermore besides MySQL table_cache Innodb maintains its own (called data dictionary) which… more than MyISAM and the total size on disk was 12GB in .ibd files plus some space allocated in system tablespace…. I used MySQL 5.4.2 for tests which should be as good as it gets in terms of optimizations in this…