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

Correct maximum recommended clients per member #1536

Merged
merged 1 commit into from
Feb 12, 2025
Merged

Correct maximum recommended clients per member #1536

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions docs/modules/clients/pages/client-overview.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,13 @@ Clients are available for xref:java.adoc[Java], xref:dotnet.adoc[.NET], xref:pyt
==== Maximum number of client connections per member

The maximum recommended number of clients per member is 100.
By default, members have `core count * 20` threads that handle all the requests.
For example, if a member has 4 cores, it will have 80 threads available to handle requests.
Members use different executors, each with a different thread count, for handling different types of client message tasks:

* Query tasks: `core count` threads
* Blocking tasks: `core count * 20` threads
* All other tasks: `core count` threads

These values, as well as each member's xref:cluster-performance:threading.adoc#io-threading[I/O Thread] counts, need to be taken into consideration when determining the appropriate client connection limits for clusters.

==== Serialization in client/server mode

Expand Down
Loading