Home/ Questions/Q 42473
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T15:20:37+00:00

I’m wondering, how expensive it is to have many threads in waiting state in

  • 0

I’m wondering, how expensive it is to have many threads in waiting state in java 1.6 x64.

To be more specific, I’m writing application which runs across many computers and sends/receives data from one to another. I feel more comfortable to have separate thread for each connected machine and task, like 1) sending data, 2) receiving data, 3) reestablishing connection when it is dropped. So, given that there are N nodes in cluster, each machine is going to have 3 threads for each of N-1 neighbours. Typically there will be 12 machines, which comes to 33 communication threads.

Most of those threads will be sleeping most of the time, so for optimization purposes I could reduce number of threads and give more job to each of them. Like, for example. reestablishing connection is responsibility of receiving thread. Or sending to all connected machines is done by single thread.

So is there any significant perfomance impact on having many sleeping threads?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. For most cases, the resources consumed by a sleeping thread will be its stack space. Using a 2-threads-per-connection-model, which I think is similar to what you’re describing, is known to cause great scalability issues for this very reason when the number of connections grow large.

    I’ve been in this situation myself, and when the number of connections grew above 500 connections (about a thousand threads), you tend to get into lots of cases where you get OutOfMemoryError, since the threads stack space usage exceeds the maximum amount of memory for a single process. At least in our case, which was in a Java on 32 bit Windows world. You can tune things and get a bit further, I guess, but in the end it’s just not very scalable since you waste lots of memory.

    If you need a large number of connections, Java NIO (new IO or whatever) is the way to go, making it possible to handle lots of connections in the same thread.

    Having said that, you shouldn’t encounter much of a problem with under a 100 threads on a reasonably modern server, even if it’s probably still a waste of resources.

    • 0