Excuses, excuses, excuses... Login and vote now.
By jj83777
via tutorials.jenkov.com
Published: Jul 04 2008 / 02:57
This is text no. 4 in a series on multithreaded servers in Java. This text describes
a thread pooled server design. Earlier designs shown in this trail are a singlethreaded
and a thread-per-connection design. The series will get more server designs in the
future.
Comments
AlainODea replied ago:
It would be really neat to have a load aware ExecutorService in java.util.concurrent that holds back jobs if CPU or Memory are nearly peek utilization. It would make it a lot easier than the current guesswork of establishing an arbitrary limit on a fixed thread pool.
Jakob Jenkov replied ago:
haha, yes, that would be cool!!! But it isn't possible to read the average CPU load from Java, is it?
albert123 replied ago:
I think you are right Jakob, in that you can't read the cpu load. However, what about setting the priority of the thread to the lowest possible?
Voters For This Link (11)
Voters Against This Link (0)