RE: [ActiveDir] Windows threads?

[Mike Hogenauer]

Thanks,   So far the problem now seems to be related to memory and Java.   Thanks for all the help, advice.   Mike   From: Eric Fleischman [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 04, 2004 7:38 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Windows threads?   Context switching will be painful here with 3k threads on not-serious hardware yes.   More generally, you’ll be hardware-constrained before you’ll really need to think about Windows issues. Things like /3gb and pae need to be considered, but short of that, you shouldn’t have any Windows issues that I’m aware of. If you do have any Windows perf issues, the standard slew of perfmon data (I go with all counters) would be a good start.   It’s also worth considering what your app is doing. If you have a thread that is doing some work and asking for something from the OS, other threads might be started too. For example, assume you have a thread that makes calls across secure channel. That will spin up threads in netlogon and you might hit other perf bottlenecks (like MaxConcurrentAPI). So it isn’t as simple as how many threads do I have, what they do is very relevant.   No simple answers here, sorry.   ~Eric     From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe Sent: Sunday, May 02, 2004 10:33 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Windows threads?   The number of threads would be a function of how the threads were using some key memory (amount of stack requested for instance ) and what is allocated by the linker options. I.E. Depending on how the program is compiled/linked, it could have differing numbers of threads. I think I recall once someone saying that in their testing they got a 2K box up to about 3000 threads for a single process. However, that isn't really realistic unless those threads are mostly sitting dead. ~Eric will probably pipe up with details if he is listening but you will get smacked around with context switching well before hitting 3000 threads in a process if the threads were doing any real work besides sitting and waiting for something.   With windows apps, generally better to look into thread pooling versus spawning lots of threads.   Not an AD issue in any way shape or form, this is entirely the realm of the application.  :o)     joe       From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Hogenauer Sent: Thursday, April 29, 2004 3:25 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] Windows threads? Does anyone know if you can increase or limit the number of threads that Windows can handle? If so is it avail in Group policy any where or just registry?     Thanks   Mike   Mike Hogenauer Sr Network administrator Rendition Networks, Inc. 10735 Willows Rd NE, Suite 150 Redmond, WA 98052 425.636.2115 | Fax: 425.497.1149