Thread management

[Henrik]

Hello, I start at least 4 threads in my program (besides the main program thread). They all have ::WaitForSingleObject(...); in them, one is for file notification update, one is for other stuff, anyway, my question is, how much does this IMPACT on program speed & memory consumption in general (depending on CPU and memory)? (I'm working on a small file manager app coded in MFC). If anyone got any comments I'm happy to here them. How many threads could one run with ::WaitForSingleObject(...); in them before it would get noticable (depending on CPU and memory)?... How many threads does a normal window program run, and a Windows 95/98/XP session in general? So all you thread experts, gimme comments! :cool: Cheers, Henrik

[Michael Dunn]

A thread that is blocked in a WaitFor...() call uses no CPU time. If all your threads are running, the CPU will be doing more context-switching, which is an expensive operation (on the order of 200 CPU cycles, IIRC). Each thread uses memory, of course, for its stack and whatever state info the OS keeps on it. But if your threads are blocking for the majority of the time, I don't think you'd run into problems. --Mike-- http://home.inreach.com/mdunn/ The Signature, back by popular demand: Buffy. Pajamas.