influxdata / influxdata/influxdb
Optimize "first" and "last" aggregate flux queries
Open
Nobody has claimed this yet.
area/2.x
area/flux
area/performance
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Flux aggregate queries using "first" and "last" are generally slower than their InfluxQL equivalents, particularly for "bare" aggregate queries, and aggregate queries involving grouping. This issue is for optimizing these queries so that the Flux versions perform comparably to the InfluxQL queries.
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
Start by comparing Flux and InfluxQL performance for bare first/last aggregate queries and for queries involving grouping. Measure the current behavior and identify the query paths responsible; done means the relevant Flux queries perform comparably to their InfluxQL equivalents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100