June 20, 2013

Post: MySQL Query Patterns, Optimized - Webinar questions followup

table to store an interim result set, and then use that toto refactor manually.  There could also be some cases where optimizing a query automatically would be more costly than just running the query in

Post: MySQL 5.6 - InnoDB Memcached Plugin as a caching layer

to use a caching layer to store expensive result sets or objects.  Some typical use cases include: Complicated querytable While there are increases in both operations, there are some tradeoffs to consider: Cost of additional memcached hardware Cost of operations time to

Post: MySQL Slow query log in the table

… 100% compatible to standard format as TIME type which is used to store query execution time and lock time does not store fractions of the second. Today I’ve got some time to play with tablehow many queries were accumulated in the logs or finding 10 last queries is not fast. The good thing however you’re allowed to change table to

Post: A micro-benchmark of stored routines in MySQL

Ever wondered how fast stored routines are in MySQL? I just ran a quick micro-benchmark to compare the speed of a stored function against… first table shown above, but the further two rows are not shown. The query can’t be optimized to use indexes, and the stored function is opaque to the optimizer. This is why I purposefully wrote the subquery badly in the first query

Post: How Percona does a MySQL Performance Audit

how to do read-write splitting without breaking the user experience, how to take online non-blocking backups, or things like that. But in…the desired modifications to the query or the table. We explain how to interpret what we… stored procedures, which are more difficult to analyze because you have to

Post: How to recover deleted rows from an InnoDB Tablespace

how it could be possible to recover, on some specific cases, a single table from a full backup in order tostored in a single directory with some subdirectories inside, one for every single index in the table

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

tables on which query depends on. If not you need to re-generate the query result. Removing of stale queries inqueries, for which tracking exact rows used from query syntax may be hard. Query Cache Storage Engines MySQL Query Cache now stores queries in

Post: Air traffic queries in InfiniDB: early alpha

how to get real size, and also explains what takes so much space. Queries First count start queryTABLES, as not supported by InfiniDB. Other queries: (again look on comparison with other engines in Google Spreadsheet or in summary table at the bottom) Query

Post: Visualization tools for pt-query-digest tables

query-digest you can store samples of each query into query_review table and historical values for review trend analysis into query_review_history tableto figure out what to optimize and how to track performance over time. Anemometer relies on the Percona Toolkit to do the slow query

Post: Using VIEW to reduce number of tables used

table reopens needs to happen which requires table header modification, which is costly. Of course if you can simply rewrite software to storeto ensure we do not insert data in the view which will be invisible. The VIEW approach works for SELECT, UPDATE, DELETE queries