# pct total min max avg 95% stddev median # This item is included in the report because it matches -limit. # 20 0x3D533D57D8B466CC 2.4209 0.5% 15 0.161391 SELECT mt_entry mt_placement mt_categoryĪbove this output are histograms of these 20 top worst-performing queriesĮxample of the first entry's histogram # Query 1: 0.77 QPS, 0.28x concurrency, ID 0x812D15015AD29D33 at byte 0 _ # 11 0x9B9092194D3910E6 5.8124 1.2% 57 0.101973 SELECT content_specialitem content_basecontentitem advertising_product organizations_neworg content_basecontentitem_item_attributes # 8 0圆C6318E56E149036 8.8294 1.8% 44 0.200667 SELECT schedule_occurrence schedule_eventschedule schedule_event schedule_eventtype schedule_event schedule_eventtype schedule_occurrence.start # 3 0x5E994008E9543B29 16.1608 3.3% 46 0.351321 SELECT schedule_occurrence schedule_eventschedule schedule_event schedule_eventtype schedule_event schedule_eventtype schedule_occurrence.start From that post, here is sample output of the query profiling done by mk-query-digest: # Rank Query ID Response time Calls R/Call Item In my old post, I suggested using mk-query-digest instead of the general log or slow log. In the DBA StackExchange I answered MySQL general query log performance effects. V/M The Variance-to-mean ratio of response timeĮXPLAIN If -explain was specified, a sparkline see -explain R/Call The mean response time per executionĪpdx The Apdex score see -apdex-threshold for details Response time The total response time, and percentage of overall totalĬalls The number of times this query was executed Rank The query's rank within the entire set of queries analyzed
0 Comments
Leave a Reply. |