The Wayback Machine - https://web.archive.org/web/20211122003905/https://github.com/dotnet/aspnetcore/issues/38558
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

Signalr MaxBuffersize settings causing large increase in memory on client #38558

Open
vinaykapoor opened this issue Nov 21, 2021 · 0 comments
Open

Comments

@vinaykapoor
Copy link

@vinaykapoor vinaykapoor commented Nov 21, 2021

I am using the following options
Signalr Hub options //data publisher
options.TransportMaxBufferSize = 65536;
options.ApplicationMaxBufferSize = 0;
sig.MaximumReceiveMessageSize = 65536;

and on the Signalr .NET Client HubConnection option
options.TransportMaxBufferSize = 65536;
options.ApplicationMaxBufferSize = 0;

I have began noticing my applications memory increase very quickly and touches around 20GB after 3-4 hours of application run all while my CPU is well below 10%.
It looks like the back pressure causes the memory to increase.

Will it be better if I assign ApplicationMaxBuffersize to a value like 65536 (65MB? If the unit of each of these properties in MB ). It would help to have that in the api's documentation or intellisense.
I was refering to the final check in made under #35107.

If you could suggest how to set the app buffer size to 2GB and send & recv buffer size to 65MB for both signalr hub publisher and Signalr .NET Client subscriber, I will really appreciate it. Right now I am guessing how to avoid the memory increase.

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants