June 19, 2013

Post: Should we give a MySQL Query Cache a second chance ?

queries have to be invalidated from the query cache… which can take a lot of time if you have millions of queriesa Summary I believe there is a lot of things which can be done to Query Cache to make it cool again. The question is whenever anyone from “MySQL

Post: Working with large data sets in MySQL

to take a lot of time. Think about 500GB table for example – ALTER TABLE make take days or even weeks depending on your storage engine and set of

Post: Onsite and Remote - getting best of both worlds

takes a lot of time) – migration projects, any forms of scripting, implementation (writing queries), hands on setting up MySQLfaster. Another trick to make remote work successful is to be very clear in your instructions especially if you’re not going to be available to

Post: The story of one MySQL Upgrade

to check only limited number of samples for each query type – otherwise it can take a lot of time. Running mk-upgrade with these queriesMySQL 4.1 to 5.0 had a lot of different issues than upgrade from MySQL 5.0 to

Post: How Percona does a MySQL Performance Audit

a lot of things like how to build for massive scalability, how to do read-write splitting without breaking the user experience, how to takeA lot of times, customers will tell us up front to limit the work to some number of hours, such as 3 hours. Knowing this ahead of time gives us a

Post: Flexviews - part 3 - improving query performance using materialized views

takes a very long time to refresh: mysql> call flexviews.refresh( -> flexviews.get_id(‘demo’,'complete_example2′),’BOTH’,NULL); Queryfaster than the latter. I also showed how you can combine both types of views together. The complete method examples show how to create a

Post: Why you should ignore MySQL's key cache hit ratio

to appreciate that tuning by ratio is a waste of time! The Oracle folks arrived at this conclusion a long time before the MySQL world started toto reduce Key_reads, we might make the database server faster overall, and perhaps the query of interest will accidentally get faster

Post: MySQL 5.6.10 Optimizer Limitations: Index Condition Pushdown

of the MySQL 5.6.10 optimizer. Other interesting things to notice: ICP is a great new feature that already saved us a lot of execution time, probably its cost has to be tuned better in the feature. There are more ways to make a query faster

Post: Is your server's performance about to degrade?

queries per second and higher, lots of memory, lots of CPU cores, and most queries are running faster than one millisecond; some in the 50 tohow to make mk-query-digest parse 2GB of slow query log with only 37MB of memory, and for our generous sponsor who paid for that work

Post: How to calculate a good InnoDB log file size

takes a long time.  That much Peter covered really well.  But how do you choose that size? I’ll show you a rule ofa more active write workload. Perhaps you’re inserting a lot of big rows or something. In this case you might want to make