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

Default ServiceBusOptions.MaxConcurrentCalls Property Leads to Poor Debugging Experience #3113

Open
Mike-E-angelo opened this issue Nov 9, 2024 · 0 comments

Comments

@Mike-E-angelo
Copy link

Hello Azure WebJobs SDK Team,

I recently found an issue with the ServiceBusOptions.MaxConcurrentCalls Property and wanted to be sure you are aware of it.

Consider developing on a CPU with 32 processors (e.g. Ryzen 9 5950x) and having 20 WebJobs in an application. That is over 10K concurrent calls. When attempting to debug in Visual Studio, Diagnostic Tools freezes up and there are a bunch of GC calls.

I have reported this to the Visual Studio team here:
https://developercommunity.visualstudio.com/t/Insane-Amounts-of-Unmanaged-Memory-Utili/10776957

Reporting here also, for awareness and potential collaboration.

Setting this value to 64 makes this operate as expected. However, the incredible amount of GC sweeps and frozen Diagnostic Tools interface is cause for concern.

Please let me know if you require any further information and I will assist you.

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

No branches or pull requests

1 participant