Default `ServiceBusOptions.MaxConcurrentCalls` Property Leads to Poor Debugging Experience

[Mike-E-angelo]

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.

[JAdluri]

Hello @Mike-E-angelo Thank you for reporting the issue . Could you please mention the step wise procedure to reproduce the issue on our end to debug further

[Mike-E-angelo]

Hi @JAdluri thank you for your time and investigation. As I understand it, simply having 20+ web jobs that utilize a ServiceBusTrigger attribute will do the trick. Make sure you are developing on a CPU with 32 threads as the AMD 5950x has. You should see the same disruptive activity during a debugging session in Visual Studio.