Investigate use of Connection Pools for various purpose
@MikeNeilson is already working on this.
Since Sep 17, 2026.
- Dominant language
- Java
- Stars
- 28
- Forks
- 25
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 20
Description
Is your feature request related to a problem? Please describe.
We have a combination of longer running (e.g A streamed period of record pull or streamed blob data) and short running (common time series or other data request)
These are share a pool which by most indications we should keep small to maintain appropriate performance.
Describe the solution you'd like
It is possible that having separate pools for "known short", "known long", and possibly other purpose may make system operation more stable.
Describe alternatives you've considered
- Buy more compute
- Horizontal Scaling (CDA + Database) (which is really just 1)
- Do nothing an hope for the best
Additional context
Actual work on this should wait until a proper load testing system is in place.
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.
Assessment
This issue has not been assessed yet.