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

Server: Raise default max-concurrent-streams following change in gRPC #410

Closed
wants to merge 2 commits into from

Conversation

bboreham
Copy link
Contributor

What this PR does:

gRPC release 1.58.3 changed the meaning of this setting from a per-client limit to a server-wide limit, thus 100 is very low as a default.

Depending on what your server does, any default will be wrong, but I propose 10,000 as a level which should not constrict most people, which was the intention of the previous default of 100 per client.

https://github.com/grpc/grpc-go/releases/tag/v1.58.3

Checklist

  • NA Tests updated
  • CHANGELOG.md updated

gRPC release 1.58.3 changed the meaning of this setting from a
per-client limit to a server-wide limit, thus 100 is very low as a default.

Depending on what your server does, any default will be wrong, but I
propose 10,000 as a level which should not constrict most people, which
was the intention of the previous default of 100 per client.

https://github.com/grpc/grpc-go/releases/tag/v1.58.3

Signed-off-by: Bryan Boreham <bjboreham@gmail.com>
server/server.go Outdated Show resolved Hide resolved
Co-authored-by: Oleg Zaytsev <mail@olegzaytsev.com>
@bboreham bboreham marked this pull request as draft October 18, 2023 22:21
@bboreham
Copy link
Contributor Author

It seems I misunderstood the change - it is still a limit per-connection.

@bboreham bboreham closed this Oct 19, 2023
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.

None yet

2 participants