Azure-webjobs-sdk: Should ServicePointManager.DefaultConnectionLimit be changed for .NET Core projects?

[codecadwallader]

On the wiki there's an explicit recommendation to override the ServicePointManager.DefaultConnectionLimit for .NET Framework projects: https://github.com/Azure/azure-webjobs-sdk/wiki/ServicePointManager-settings-for-WebJobs

Does this recommendation apply to .NET Core projects as well?

I experimented with it over the last few days with some .NET Core projects.. and had a pretty negative outcome in one scenario.. but that may be specific to my usage.

I did raise this question before against a how-to on the the Azure docs site, but thought I should clarify directly with the relevant team. https://github.com/MicrosoftDocs/azure-docs/issues/9918

Thanks for the clarification!

[fabiocav]

Assigning this to triaged, as the default configuration and the behavior has changed in .NET Core and we need to review our guidance.

[davidhjones]

@paulbatum I'm trying to find the proper 3.x documentation to migrate from 2.x; All of the documentation I see references the 2.x (or previous) SDK. Is there an effort going on to produce 3.x SDK documentation?

[paulbatum]

@davidhjones as of right now, no. We acknowledge that there is a documentation gap with webjobs 3.x but we've not had the bandwidth to address it as of yet.

[SeanFeldman]

@fabiocav @paulbatum a year later, the wiki is gone and this issue was not actioned. Would be good to at least capture some of the recommendations in this issue until documentation is ready.

[fgbaezp]

So, do we need to change this knob for .Net Core projects or not?

[paulbatum]

Just wanted to mention that I restored the wiki page since it was still applicable for running WebJobs SDK on .NET Framework.

Unfortunately at this time I cannot answer @fgbaezp 's question about what guidance is applicable for .NET Core.

[wboevink]

Any new guidance?