May 25, 2012

Post: MariaDB 5.3 is released as GA!

…different) offer flexibility in schemas Microsecond time resolution for DATETIME and similar time-based types, as well as microseconds in SHOW PROCESSLIST Group commit for the binary log makes the server much faster with the binary log enabled Faster queries

Post: Updated msl (microslow) patch, installation walk-through!

… at run time with both SET SESSION and SET GLOBAL. long_query_time=# Log all queries that have taken more than long_query_time microseconds to execute to file. This option is standard MySQL, however after you apply the patch, it will no longer take time

Post: What time 18446744073709550.000 means

… like this in timestamps. Periodically in our patches there was Query_time: 18446744073709550.000 in slow.log file (well, it was fixed… own time. Usually difference between generators is very small (microseconds matter), but it appears this difference is enough to get negative time. It happens when your query started on one…

Post: Slow Query Log analyzes tools

… Patching Slow Query Logging – First thing we did is created a Patch which allows you to specify slow query time in microseconds rather than seconds and allows you to log all queries in slow query log by setting long_query_time=0 This…

Post: The new cool MySQL patch has landed! Check your queries performance!

… choose to log all queries to see those which take less than 1s. Now long_query_time is in microseconds and you can set it for example to 300000 which is 0.3s! # Query_time: 0.503016 Lock_time: 0… not used: # Time: 071031 20:03:16 # User@Host: macko[macko] @ localhost [] # Thread_id: 12 # Query_time: 0.026385 Lock_time: 0.000158 Rows…

Post: Backport of micro-time patch to mysql 4.1

… slow-log queries. The patch allows to specify time of slow queries in microseconds and is very helpful in a fight with problematic queries. 4…

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

….82.196] # Thread_id: 3329398998 Schema: app_db # Query_time: 0.306486 Lock_time: 0.000000 Rows_sent: 0 Rows_examined: 0 Rows…) time to execute. To give some context, normally these take 75 microseconds. I can see it clearly when I scan the slow queryquery cache) are executing in no more than 12 microseconds, worst-case. So the contention that’s blocking these queries for shockingly long times

Post: Microslow patch for 5.1.20

… parameter –long_query_time=n or by setting MySQL system variable with SET [SESSION|GLOBAL] long_query_time=n. The value is in microseconds (0…. long_query_time value was meant to set time limit in microseconds, but in the end it was always compared to seconds of query execution time

Post: Percona Server 5.1.47-rel11.0

… error code 1592. Added the –microseconds_in_slow_query_log option to use microsecond precision for the slow query log’s timestamps (issue #358412… –use_global_long_query_time. Added the –query_cache_strip_comments option to strip comments from query before using it in query cache. Added a…

Post: How To Test Your Upgrades - pt-upgrade

…. Capture your production queries, we recommend either slow query log (use long_query_time = 0) or tcpdump (other types supported by pt-query-digest’s… site = ? Looking at the sample above, there are microsecond differences between the query times. The most important is the average (avg) which tells…