Re: [ADVANCED-DOTNET] Massive Use of Threads Issue

2002-07-03 Thread Ben Kloosterman
Further comments Having large amounts of blocked threads is not an issue just a waste of resources. A pool is more resource effecient with a very minor overhead ~ 10 ms ( 15 ms on a multi processor machine) . Again if you need finer granularity dont use a managed environment.

Re: [ADVANCED-DOTNET] Massive Use of Threads Issue

2002-07-03 Thread Ian Griffiths
Ben Kloosterman [EMAIL PROTECTED] wrote: Having large amounts of blocked threads is not an issue just a waste of resources. A pool is more resource effecient with a very minor overhead ~ 10 ms ( 15 ms on a multi processor machine) . What does that mean? What's a 10ms overhead? 10ms

Re: [ADVANCED-DOTNET] Massive Use of Threads Issue

2002-07-02 Thread Ben Kloosterman
Message- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED]]On Behalf Of David Williams Sent: Monday, 1 July 2002 9:54 PM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Massive Use of Threads Issue Andy, you are correct in that the software library that I have

Re: [ADVANCED-DOTNET] Massive Use of Threads Issue

2002-07-02 Thread Thomas Tomiczek
) [mailto:[EMAIL PROTECTED]] Sent: Montag, 1. Juli 2002 13:45 To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Massive Use of Threads Issue Thomas, I'm surprised that you can provide such an apparently definitive answer without knowing more about the environment. *** Some have this knowledge

Re: [ADVANCED-DOTNET] Massive Use of Threads Issue

2002-07-02 Thread Mcmullan, Andy (Andrew)
Thomas On most of these issues we could argue the toss all day and get nowhere. But there are a couple of concrete points I'd like to pick up on. You say: Threads mean that a thread scheduler has to check them regularly and has to blow it's performance on this. My understanding is that with

[ADVANCED-DOTNET] Massive Use of Threads Issue

2002-07-01 Thread David Williams
It the component design that I have, it appears that I am going to end up with something on the order of 300 threads running. My question is simple. Is this number of threads going to cause me massive headaches? Okay, before you ask, the reason that I have this design is that I have a number of

Re: [ADVANCED-DOTNET] Massive Use of Threads Issue

2002-07-01 Thread Thomas Tomiczek
them. Use pooled database connections. Regards Thomas Tomiczek THONA Consulting Ltd. (Microsoft MVP C#/.NET) -Original Message- From: David Williams [mailto:[EMAIL PROTECTED]] Sent: Sonntag, 30. Juni 2002 22:37 To: [EMAIL PROTECTED] Subject: [ADVANCED-DOTNET] Massive Use of Threads Issue

Re: [ADVANCED-DOTNET] Massive Use of Threads Issue

2002-07-01 Thread Mcmullan, Andy (Andrew)
. database access) is required during each call, etc etc. Andy Mc -Original Message- From: Thomas Tomiczek [mailto:[EMAIL PROTECTED]] Sent: 01 July 2002 10:56 To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Massive Use of Threads Issue You are dead :-) Frankly, tell your hardware