> use the custom threadpool of Mike Woodring at > http://www.bearcanyon.com/dotnet/ > some swear by it > > Stefan
Before he does that... Paul - what kind of application are you writing/running in? If you're in a windows forms app, console app, or NT service written using managed code, I'd probably just recommend going with the built-in threadpool. In those scenarios you "own" the process, so you won't be sharing the pool (or hogging the pool) with anyone else. And if you hit the default 25 thread maximum and still have CPU cycles to spare on your machine, it's a lot easier to use the ICorThreadPool[1] interface to up the maximum thread alotment than it is to use a custom thread pool like [2]. If you don't have CPU cycles to spare, then there's no point in adding more threads to the situation. A custom thread pool is more useful when you want to leverage a thread pool, but segregate it from the normal pool (for example, setting up a separate pool of a *few* threads running at a lower priority than the built in thread pool); or for ASP.NET scenarios were you're trying to implement IHttpAsyncHandler for long-running we pages, and (again) you want to perform those operations on a pool of threads that's segregated from the one that's normally used for ASP.NET request processing (so that your long running operations don't reduce the ability of ASP.NET to process HTTP requests for other resources). If you are in that camp of performing these operations in the context of an ASP.NET page, then I recommend you read Fritz Onion's article on the topic[3] before you go too far down this road. -Mike http://www.bearcanyon.com [1] http://www.bearcanyon.com/dotnet/#tpcontrol [2] http://www.bearcanyon.com/dotnet/#threadpool [3] http://msdn.microsoft.com/msdnmag/issues/03/06/Threading/default.aspx =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
