cloudfoundry / cloudfoundry/capi-release
Evaluate impact of db connection pool on throughput and performance
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 24
- Forks
- 110
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 8
Description
Context
Currently each CC consumes 20 db connections by default. For Amazon RDS(postgres) the connection limit is 5000 LEAST({DBInstanceClassMemory/9531392}, 5000) see https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Limits.html
When also taking CC workers into account one can estimate rughly 200 CC instances can be started and no further scaling is possible. Other hyperscales have similar restrictions.
Can we tweak this value down safely to increase the number of CC instances and thus allow for higher throughput and load without optimizing the implementation in particular.
Acceptance Criteria
- We have a document showing how changing this parameter influeces 1. troughput and 2. performance
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
The payload names no files, tests, or entry points. Start by locating the configuration that sets the default of 20 database connections per CC, then compare several pool sizes under representative CC worker loads. Document how each value affects throughput and performance, as required by the acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- backend, databases, performance
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100