Do waiting threads hinder system performance?

Imagine having 6000 or 10,000 threads that are not running but waiting or blocked. Would such a system hinder the overall performance of the system on which they are running?tx
[190 byte] By [tx56ma] at [2007-11-27 5:40:17]
# 1
since they are objects, even if paused, they do exist in the memoryso i think the answer is yes
calvino_inda at 2007-7-12 15:16:33 > top of Java-index,Java Essentials,Java Programming...
# 2

Threads that are waiting for I/O, or doing wait()/notify(), or Thread.sleep(), do not consume CPU time. (Assuming a normal, non-silly operating system.)

Threads do consume memory. Each thread needs a stack, and the operating system kernel may have non-pageable data structures for each thread.

I would try to re-think the program design rather than have thousands of threads. I've seen bad things start to happen at less than 1000 threads on a common operating system.

sjasjaa at 2007-7-12 15:16:33 > top of Java-index,Java Essentials,Java Programming...
# 3
thanks to both :) yes I have my own doubts about starting 10000 and leaving them empty ... just wanted to confirm! I will re-think the design as sugested :)Thanks to both :)tx
tx56ma at 2007-7-12 15:16:33 > top of Java-index,Java Essentials,Java Programming...