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.

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

sources/config_reader.c: new default client_max_routing #715

Merged
merged 1 commit into from
Nov 15, 2024

Conversation

rkhapov
Copy link
Collaborator

@rkhapov rkhapov commented Nov 15, 2024

Default per worker 16 value should be increased to achive more CPU utilization and client connections rate.

After testing some client connection parallelism i learn that there should be ~ 60-80 client connections per worker to get 100% of cpu loading (with non-localhost connections)

So this patch increases 16 to 64

benchmarks/client_max_routing might be used for future learning

Default per worker 16 value should be increased to achive
more CPU utilization and client connections rate.

After testing some client connection parallelism i learn that
there should be ~ 60-80 client connections per worker to get 100% of cpu loading
(with non-localhost connections)

So this patch increases 16 to 64

benchmarks/client_max_routing might be used for future learning

Signed-off-by: rkhapov <r.khapov@ya.ru>
@rkhapov rkhapov merged commit f081cf9 into master Nov 15, 2024
1 check passed
rkhapov added a commit that referenced this pull request Nov 15, 2024
Default per worker 16 value should be increased to achive
more CPU utilization and client connections rate.

After testing some client connection parallelism i learn that
there should be ~ 60-80 client connections per worker to get 100% of cpu loading
(with non-localhost connections)

So this patch increases 16 to 64

benchmarks/client_max_routing might be used for future learning

Signed-off-by: rkhapov <r.khapov@ya.ru>
Co-authored-by: rkhapov <r.khapov@ya.ru>
(cherry picked from commit f081cf9)
Signed-off-by: rkhapov <r.khapov@ya.ru>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants