[MDEV-4568] Port Percona response time distribution as audit plugin Created: 2013-05-23  Updated: 2013-08-18  Resolved: 2013-06-18

Status: Closed
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Sergey Vojtovich Assignee: Sergey Vojtovich
Resolution: Fixed Votes: 1
Labels: plugins

Attachments: Text File qrtp.patch    
Issue Links:
Relates
relates to MDEV-4904 Add query cache hit information to Pe... Stalled

 Description   

The slow query log provides exact information about queries that take a long time to execute. However, sometimes there are a large number of queries that each take a very short amount of time to execute. This feature provides a tool for analyzing that information by counting and displaying the number of queries according to the the length of time they took to execute. The user can define time intervals that divide the range 0 to positive infinity into smaller intervals and then collect the number of commands whose execution times fall into each of those intervals.

http://www.percona.com/doc/percona-server/5.5/diagnostics/response_time_distribution.html

This feature is almost perfect to be ported as audit plugin. There are a few constraints though:

  • FLUSH QUERY_RESPONSE_TIME. We will substitute it with system variable like "query_response_time_flush". Update of this variable will trigger flush.
  • we won't port old-style "have_response_time_distribution" variable.
  • we probably won't port old-style "SHOW QUERY_RESPONSE_TIME".


 Comments   
Comment by Sergey Vojtovich [ 2013-05-30 ]

Initial prototype

Comment by Sergey Vojtovich [ 2013-05-30 ]

Sergei, please review attached patch.

Comment by Sergey Vojtovich [ 2013-05-31 ]

Please review updated patch.

Comment by Sergei Golubchik [ 2013-06-03 ]

reviewed, ok to push

Comment by roberto spadim [ 2013-08-15 ]

how query cache will work here?
it will be placed at 0.01ms to 0.1ms for example? instead of the default query time?

could we add a new column
query_cache ENUM('Y','N') not null default 'N'
in this case we know what kind of query was executed

Comment by roberto spadim [ 2013-08-15 ]

or maybe... since the today table is running at percona, add two more fields...

count_query_cache, total_query_cache

to know the "no query cache used" values we could execute
SELECT (count-count_query_cache)
and
SELECT (total-total_query_cache)

Comment by roberto spadim [ 2013-08-18 ]

please check https://mariadb.atlassian.net/browse/MDEV-4904
i add query cache information
maybe it could be usefull...

Generated at Thu Feb 08 06:57:25 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.