My ASP.NET application is a download application (without pages) that reads huge binary files (1-2 GB → more than 1 hour of loading time with resume support) from the local network and transfers them to web clients (each request → one large binary answer, so there is no text / html answer at all). I use an HTTP handler (.ashx) instead of a page (.aspx) to process requests. Using the main thread and the main thread of the producer and consumer pattern (from the ASP.NET thread pool) creates another thread, and together they perform the task. At the end, both threads exit (return to the pool).
So, I have a lengthy request using threads from a thread pool, which is not recommended at all, but I don't have any page in my application, is this still a bottleneck using threads from an ASP.NET thread pool?
Environment: Server 2008 64-bit, IIS 7.0, and .NET 4.0
What considerations should be taken for this scenario? Any comments are welcome.
source
share