June 19, 2013

Post: MySQL caching methods and tips

increasing probabilitycache that you intend to retrieve again. Storing data in the cache that you won’t read again also increases response time in yourtable always exists, and should be fast to access, since it can be indexed appropriately for your queries. Using INSERT .. SELECT for summary tables

Post: MySQL Query Cache

cache. If you need larger queries to be cached you might increase it, if you most important queries are smaller youprobably the most popular distributed caching system and it works great. I should write an article comparing performance of various caching

Post: Economics of Performance Optimization

tables, significant schema changes, use of replication, caching, using memcached, sphinx, implementing proper web cachingyou should think if your assessment of MySQL scaling abilities is the right one. It well may be you

Post: Why MySQL could be slow with large tables ?

you‘ve been reading enough database related forums, mailing lists or blogs you probablyyou should be concerned if you‘re dealing with very large data sets are Buffers, Indexes and Joins. Buffers First thing youincreasedcaches. With proper application architecture and table design you

Post: When would you use SAN with MySQL ?

caching. SAN can have a lot of cache though servers can typically have more. If you can afford SAN you shouldyou should also evaluate external directly attached storage, SSDs, Increasing

Post: MySQL Server Memory Usage

cache_size. If you‘re using MyISAM seriously you can also add the size of Operation System cache you would like MySQL to use for your tableCache and other applications. For 32bit envinronment you also should keep 32bit limits into account and probably

Post: What to tune in MySQL Server after installation

should use smaller values. innodb_flush_log_at_trx_commit Crying about Innodb being 100 times slower than MyISAM ? You probably… size your cache so it is large enough to keep most of your tablestables (remember each connection needs its own entry) if you have many connections or many tables increase

Post: Thoughts on MySQL Replication

increasing of write load can cause the trouble. Assume you have same master and yourshould be used only for absolutely critical updates. Third one is to use cache – something like memcached, besides pure caching

Post: SHOW INNODB STATUS walk through

should be 16K – page size, for full table scan or index scan read-ahead may be performed which can increase…2 log writes are done to OS cache, and being sequential writes these logs …you can learn if your buffer pool is sized well – if you have constantly a lot of pages free, it probably means your

Post: MySQL Crash Recovery

your workload. I should also mention if you have innodb_file_per_table=1 your recovery speed will depend on number of Innodb tables youyou restart MySQL server its caches (key_buffer, innodb_buffer_pool, query_cache,table_cache) are cleaned, so may be OS caches