All work
- [QAN] Improve query performance when looking up filtersPMM-13939Alex Demidoff
- QAA Verification for Mysql QAN Perfschema query count with different DB for same queryPMM-13936
- GetReport and GetFilteredMetricsName fail if Plan summary filter's value with brackets is selectedPMM-13897Nailya Kutlubaeva
- Need to integrate pt-index-usage tool in PMM to identify duplicate and unused index reports.PMM-13811
- pmm-agent crashed at query.Fingerprint due to query including a column named "value"PMM-13807Nailya Kutlubaeva
- Probably not used endpoint in QAN - GetMetricsNamesPMM-13793
- Wrong count used for some Mongo metrics in QANPMM-13788Jiří Čtvrtka
- Make pg_stat_monitor the default for PMM's internal databasePMM-13716
- Realtime QAN Slow/locking/CPU/Memory intensive Queries Monitoring Dashboard for MySQL/MariaDB/MongoDB/PostgreSQLPMM-13710
- More precise data calculation from QAN
PMM-13695Michael Okoko - When using a non-default pg_stat_statements.max value, the calculated QPS displayed in QAN may be wrong.PMM-13694Michael Okoko
- grpc: received message larger than maxPMM-13686Resolved issue: PMM-13686
- [QAN] Not precise time metrics in case of "Enabled query plan" in PG.PMM-13651
- [QAN] Way how AVG is computed for PG.PMM-13650
- Define default retention for system log tables or disable themPMM-13644talha.rizwan
- PMM QAN is Broken when Query having Explain KeywordPMM-13636Resolved issue: PMM-13636Matej Kubinec
- Query Analytics shows only "n/a" in Database & User Name filters (only for MySQL/MariaDB nodes)PMM-13609
- MongoDB plan tracking on executionPMM-13603Resolved issue: PMM-13603Jiří Čtvrtka
- Prevent plain password in QAN for PG extensionsPMM-13600
- Implement QAN DDL/DML filtersPMM-13588
- qan_postgresql_pgstatements_agent tries to extract tables from truncated queriesPMM-13579Resolved issue: PMM-13579Nurlan Moldomurov
- Query plan presentation doesn't honour filter in QANPMM-13574
- Add scraping of sys.innodb_lock_waits for additional QAN dataPMM-13565Resolved issue: PMM-13565
- pmm-agent flooding MongoDB with connectionsPMM-13530Resolved issue: PMM-13530
- Allow cleartext passwords when adding MySQL to PMMPMM-13513
- Provide QAN UI feedback when settings are sub-optimalPMM-13512
- Remove truncated queries from QAN, or give better feedbackPMM-13511
- QAN Explain sometimes uses older ExamplePMM-13510
- don't show "pmm queries" from QANPMM-13484
- RBAC for QANPMM-13478Resolved issue: PMM-13478
- Extend QAN for MongoDBPMM-13465Jiří Čtvrtka
- Improve the QAN filter panel UIPMM-13462
- QAN PostgreSQL EXPLAIN plan is not providing enough details like MySQLPMM-13455Roma Novikov
- PMM Server - QAN - No Data on details tab for selected query.PMM-13452Resolved issue: PMM-13452Jiří Čtvrtka
- Error when analyzing MySQL queries in QAN in PMMPMM-13445Resolved issue: PMM-13445
- Full SQL Text including comments for MySQL QANPMM-13395
- Improve query fingerprint presentationPMM-13374Resolved issue: PMM-13374Nurlan Moldomurov
- Remove the "1 item" "2 item" etc from "Examples" section of MongoDB QANPMM-13372Resolved issue: PMM-13372Dora Cretu
- Use the value of the field QUANTILE_99 when the mysql query source is Performance_schemaPMM-13363Roma Novikov
- Add additional columns options to QANPMM-13349
- [QAN] Problem with run explain on examples with ISODate function.PMM-13308Jiří Čtvrtka
- Fully featured QAN without exposing real examples to some usersPMM-13304
- max query length is ignored for pg_stat_statements.PMM-13288Resolved issue: PMM-13288Nurlan Moldomurov
- Discrepancy in PMM 2.42.0 between QAN and InnoDBPMM-13281Jiří Čtvrtka
- The use of pg_stat_statements by PMM generates a load of temporary tablesPMM-13221Aaditya Dubey
- Example tab displaying just $ values rather than actual values for the slow queries in the QAN for PostgreSQL DBPMM-13195
- QAN->PGSQL->Plan tooltip not displayedPMM-13176Resolved issue: PMM-13176Yash Sartanpara
- PG 17 support by Query AnalyticsPMM-13154Resolved issue: PMM-13154Nurlan Moldomurov
- MySQL/MariaDB Schemaname is empty in QANPMM-13148Jiří Čtvrtka
- Upgrade pg_query_go to v5PMM-13133Resolved issue: PMM-13133Alex Demidoff
50 of 920
[QAN] Improve query performance when looking up filters
General
Escalation
General
Escalation
Description
How to test
None
How to document
Mention this improvement in the next Release Notes.
Smart Checklist
hideDetails
Assignee
Alex DemidoffAlex DemidoffReporter
Alex DemidoffAlex DemidoffPriority
MediumComponents
Labels
Needs QA
NoNeeds Doc
NoPlanned Version/s
Fix versions
Story Points
0.1Sprint
Smart Checklist Progress
0/1Start date
Apr 16, 2025
Details
Details
Assignee
Alex Demidoff
Alex Demidoff
Reporter
Alex Demidoff
Alex DemidoffPriority
MediumComponents
Labels
Needs QA
No
Needs Doc
No
Planned Version/s
Fix versions
Story Points
0.1
Sprint
Smart Checklist Progress
0/1
Start date
Apr 16, 2025
Smart Checklist
Smart Checklist
Smart Checklist
Created April 16, 2025 at 4:16 PM
Updated 2 days ago
Activity
Show:
QAN filters (the left part in QAN UI) are known to suffer from notoriously long query times. This is because the underlying SQL SELECT query is not leveraging “DISTINCT” operator, which results in it returning tens, if not hundreds, of thousands of rows containing the same values.
Therefore, adding “DISTINCT” to the SELECT query drastically improves the time it takes QAN to process query results, which becomes noticeable even with a naked eye
To compare the number of rows returned before and after the fix, I ran the query on a local machine with 2.44 mln rows in QAN database. The difference is almost 40K rows!
Before:
After: