Ok. Ideally assuming your threads do not have locking such that they do not block each other (independent of each other) and you can assume that the work load (processing) is same, then it turns out that, have a pool size of Runtime.getRuntime().availableProcessors() or availableProcessors() + 1 gives the best results. But say, if threads … Read more
The answer revolves around the purpose of threads, which is parallelism: to run several separate lines of execution at once. In an ‘ideal’ system, you would have one thread executing per core: no interruption. In reality this isn’t the case. Even if you have four cores and four working threads, your process and it threads … Read more
Processes vs Threads In days of old, each process had precisely one thread of execution, so processes were scheduled onto cores directly (and in these old days, there was almost only one core to schedule onto). However, in operating systems that support threading (which is almost all moderns OS’s), it is threads, not processes that … Read more
You can determine the number of processes available to the Java Virtual Machine by using the static Runtime method, availableProcessors. Once you have determined the number of processors available, create that number of threads and split up your work accordingly. Update: To further clarify, a Thread is just an Object in Java, so you can … Read more
There are several different pieces of information relating to processors that you could get: Number of physical processors Number of cores Number of logical processors. These can all be different; in the case of a machine with 2 dual-core hyper-threading-enabled processors, there are 2 physical processors, 4 cores, and 8 logical processors. The number of … Read more