Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
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".
Attachments
Issue Links
- relates to
-
-
- Stalled
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| 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 wont port old-style "have_response_time_distribution" variable. - we probably wont port old-style "SHOW QUERY_RESPONSE_TIME". |
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". |
| Attachment | qrtp.patch [ 22310 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Assignee | Sergey Vojtovich [ svoj ] | Sergei Golubchik [ serg ] |
| Assignee | Sergei Golubchik [ serg ] | Sergey Vojtovich [ svoj ] |
| Assignee | Sergey Vojtovich [ svoj ] | Sergei Golubchik [ serg ] |
| Assignee | Sergei Golubchik [ serg ] | Sergey Vojtovich [ svoj ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
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
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)
please check https://mariadb.atlassian.net/browse/MDEV-4904
i add query cache information
maybe it could be usefull...
| Workflow | defaullt [ 27525 ] | MariaDB v2 [ 42738 ] |
| Workflow | MariaDB v2 [ 42738 ] | MariaDB v3 [ 61742 ] |
| Workflow | MariaDB v3 [ 61742 ] | MariaDB v4 [ 132130 ] |
Initial prototype