nextcloud / nextcloud/profiler
Do an EXPLAIN for each query and figure out which queries are not supported by index or sequence scans
Nobody has claimed this yet.
- Dominant language
- Vue
- Stars
- 11
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 17
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Feature request
Which Nextcloud Version are you currently using: (see administration page)
Is your feature request related to a problem? Please describe.
Currently it's not trivial to figure out how well a query is supported by indices or sequences. This either requires using PMM, validating the query manually or extract it and running EXPLAIN on it manually.
Describe the solution you'd like
The profiler should allow doing this automatically and ideally also parse the results so queries without indices or sequences can be shown as problematic without any manual work.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by locating how the profiler collects queries, then determine where EXPLAIN results could be gathered and parsed; done means queries lacking index or sequence support are automatically identified as problematic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100