If you don't vote, who will? Login and vote now.
By harris goldstone
via java.dzone.com
Published: Jun 26 2008 / 08:03
Jakob continues his concurrency series with a new installment, about thread pools: "Thread Pools are useful when you need to limit the number of threads running in your application at the same time. There is a performance overhead associated with starting a new thread, and each thread is also allocated some memory for its stack etc."
Comments
climber76 replied ago:
Hi all,
Why don't you use ScheduledThreadPoolExecutor (http://java.sun.com/javase/6/docs/api/java/util/concurrent/ScheduledThreadPoolExecutor.html)? I think it is a valid alternative to homemade thread pool managers.
Jakob Jenkov replied ago:
It is. The text also mentions that Java 5 comes with built in thread pools. The text (and the tutorial in general) merely serves as explanation of the basic theoretic issues in Java Concurrency. Once you understand the basics it is easier to understand concurrency in general, and easier to use the built-in concurrency utilities (in my opinion).
Voters For This Link (13)
Voters Against This Link (0)