May 22, 2012

Post: High-Performance Click Analysis with MySQL

you can.  You can save very large amounts of space.  Choose primary keys very carefully, especially with InnoDB tablesa lot of joins between fact and dimension tables, and so on.  With careful tweaking, many of these things can be overcome, but how much time do you

Post: Why MySQL could be slow with large tables ?

table design and understanding inner works of MySQL. If you design your data wisely considering what MySQL can do and what it can‘t youMyISAM tablestables or perform complex queries finding relationships between objects. Normalized structure and a lot of joins

Post: Innodb Performance Optimization Basics

a good balance between reasonable recovery time and good performance innodb_log_buffer_size=4M 4M is good for most cases unless youinnodb_file_per_table – If you do not have too many tables use this option, so you will not have uncontrolled innodb main tablespace growth which you can

Post: To pack or not to pack - MyISAM Key compression

MyISAM Index size: PACK_KEYS=DEFAULT – 1550K PACK_KEYS=1 – 1453K PACK_KEYS=0 – 8176K As we can see difference between 1 anddo a bit of uncompression than to traverse large memory areas. Reverse index scan performance got some 8 times faster and join

Post: Troubleshooting MySQL Upgrade Performance Regressions

can especially be helpful. Once you have spotted the query which performs differently between MySQL Server versions youinnodb-stats-method and myisam-stats-method. For Innodband MySQL 5.6 you can also store innodb stats in table so you

Post: Guidance for MySQL Optimizer Developers

tables such MyISAM or Innodb) others keep database on SSD which has completely different ratio between CPU and IO cost. Focus on Execution Methods Performance problems can be due to optimizer picking the wrong plan, such as doing full table