Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Evaluate impact of db connection pool on throughput and performance #220

Open
1 task
FloThinksPi opened this issue Jan 12, 2022 · 0 comments
Open
1 task

Evaluate impact of db connection pool on throughput and performance #220

FloThinksPi opened this issue Jan 12, 2022 · 0 comments
Labels
performance PoC Issue/PR that is part of a PoC to try out new things unscheduled

Comments

@FloThinksPi
Copy link
Member

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
performance PoC Issue/PR that is part of a PoC to try out new things unscheduled
Projects
App Runtime Interfaces Working Group
Status: Todo
CAPI Performance PoC
Status: Proposed
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cf-gitbot @FloThinksPi