influxdata / influxdata/kapacitor
Could Kapacitor query InfluxDB in parallel when creating a recording?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
I've been watching the InfluxDB logs to see the queries Kapacitor makes while creating a recording and it looks like queries are made sequentially for each batch. In our simple use case, each batch is independent. Is it possible or would it even make sense to parallelize some of this querying in order to speed up backtesting?
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 named. Start by tracing recording creation and how queries are scheduled for each batch, then determine whether independent batches can run concurrently without changing results. Done should include a justified concurrency design, preserved recording correctness, and evidence that backtesting is faster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100