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

Predictable client/server memory usage by limiting payload size #40

Open
mostroverkhov opened this issue Jul 14, 2018 · 0 comments
Open

Predictable client/server memory usage by limiting payload size #40

mostroverkhov opened this issue Jul 14, 2018 · 0 comments
Labels
enhancement

Comments

@mostroverkhov
Copy link
Member

Poroposed in rsocket/rsocket-java#514

Given accounting is number of frame based, supporting max message sizes (fragmentation aware) sounds like a good tuning parameter. I would expect to be able to size the memory of an rsocket server predictably for the number of supported clients and configured credits etc.
@whyoleg whyoleg added this to the 0.11.0 milestone Oct 18, 2020
@whyoleg whyoleg modified the milestones: 0.11.0, 0.12.0 Nov 5, 2020
@whyoleg whyoleg modified the milestones: 0.12.0, 0.13.0 Dec 8, 2020
@olme04 olme04 mentioned this issue Jul 15, 2021
Merged
@whyoleg whyoleg modified the milestones: 0.13.0, 0.17.0 Oct 5, 2022
@whyoleg whyoleg modified the milestone: 0.16.0 - Transport API/Internals rework, QUIC, Netty Nov 24, 2022
@whyoleg whyoleg removed this from the 0.16.0 - Transport API/Internals rework, QUIC, Netty milestone May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mostroverkhov @whyoleg