I’ve always been under the impression that using the ThreadPool for (let’s say non-critical) short-lived background tasks was considered best practice, even in ASP.NET, but then I came across this article that seems to suggest otherwise – the argument being that you should leave the ThreadPool to deal with ASP.NET related requests.
I am reading an article about HttpContext and CallContext and see thread-agility.
What does it mean?
Environment: Windows Server 2008 Enterprise, IIS 7.0, ASP.NET 2.0 (CLR), .NET 4.0
I’m developing a .NET 4 application that requires a backend worker thread to be running. This thread consists mostly of the following code:
I have a Redis cluster of 6 instances, 3 master and 3 slaves. My ASP .NET Core application uses it as a cache. Sometimes I get such an error:
I usually use many EF Core async methods in my web application like this:
Since the very begining of writing ASP.NET applications when I wanted to add a threading there are 3 simple ways I can accomplish threading within my ASP.NET application :
I have looked into several ‘too many clients’ related topic here but still can’t solve my problem, so I have to ask this again, for me specific case.
multiprocessing.Pool is driving me crazy…
I want to upgrade many packages, and for every one of them I have to check whether there is a greater version or not. This is done by the check_one function.
The main code is in the Updater.update method: there I create the Pool object and call the map() method.