Java线程池的目的主要有:
1) 线程池中包含固定存在和有效时间存活的线程,在执行大量并发请求时,能够节省线程创建和关闭的开销,从而提高项目的性能
2) 在一定程度上可以对线程数目做可控处理,降低CPU Starvation的风险。每个线程都要占用一定的内存,而且并不是线程数目越多,任务执行的越快,线程的上下文切换也是一个大的开销。
具体实现类,可以参考java.util.concurrent.ThreadPoolExecutor.java
1. API接口
ThreadPoolExecutor提供的主要API有:
public void execute(Runnable command); //执行一个新的任务
public void shutdown();//不再接受新的任务请求,但会继续执行之前提交的未处理的任务
public List<Runnable> shutdownNow(); //尝试去中止所有正在执行的任务,并返回正在出于等待的任务
.....
还有其他检测线程池的状态的API
2. 状态定义和设计
private static final int COUNT_BITS = Integer.SIZE - 3;
// runState is stored in the high-order bits
private static final int RUNNING = -1 << COUNT_BITS;
private static final int SHUTDOWN = 0 << COUNT_BITS;
private static final int STOP = 1 << COUNT_BITS;
private static final int TIDYING = 2 << COUNT_BITS;
private static final int TERMINATED = 3 << COUNT_BITS;
ThreadPoolExecutor定义了如上代码中的5中运行时状态。
RUNNING:正在运行,接受新的任务,并处理已经入列的任务
SHUTDOWN: 不再接受新的任务,但会继续处理在等待队列中未处理的任务
STOP: 不再接受新的任务,也不处理在等待队列中的任务,并且会尝试去中断正在处理的任务
TIDYING: 所有的任务都已经中止,并且池中线程的数目为0(当运行时状态切换到TIDYING时,会触发terminated()方法)
TERMINATED: 当terminated()方法执行完毕,则切换到了TERMINATED
几种状态的切换:
RUNNING -> SHUTDOWN(执行shutdown()方法)
(RUNNING or SHUTDOWN) -> STOP (执行shutdownNow()方法)
SHUTDOWN -> TIDYING (当等待处理的线程队列和线程池中都为空)
TIDYING -> TERMINATED(当terminated()这个钩子方法执行完毕后)
3. 结构设计
private final AtomicInteger ctl = new AtomicInteger(ctlOf(RUNNING, 0));//统计正在运行的线程数目
....
private final BlockingQueue<Runnable> workQueue;//未分配的的待处理任务
....
private final HashSet<Worker> workers = new HashSet<Worker>();//池中线程的封装类,每一个Worker关联一个Thread对象
....
具体结构如下图:
4. 任务处理流程
线程池接收的新的任务后,如果当前池中线程数没有超过CoreSize,则创建一个新的Worker(同时会创建一个新的线程对象,关联在Worker对象上)。否则,直接将任务放入待处理任务队列中。新的Worker创建,并成功添加到线程池后,会开启一个新的线程(Worker对象关联的线程)去执行Worker的run()方法。在这里,Worker委托ThreadPoolExecutor去执行实际业务处理方法,并将自己的引用暴露给ThreadPoolExecutor的runTask(Worker worker) 方法。
/** Delegates main run loop to outer runWorker */
public void run() {
runWorker(this);
}
final void runWorker(Worker w) {
Thread wt = Thread.currentThread();
Runnable task = w.firstTask;
w.firstTask = null;
w.unlock(); // allow interrupts
boolean completedAbruptly = true;
try {
while (task != null || (task = getTask()) != null) {
w.lock();
// If pool is stopping, ensure thread is interrupted;
// if not, ensure thread is not interrupted. This
// requires a recheck in second case to deal with
// shutdownNow race while clearing interrupt
if ((runStateAtLeast(ctl.get(), STOP) ||
(Thread.interrupted() &&
runStateAtLeast(ctl.get(), STOP))) &&
!wt.isInterrupted())
wt.interrupt();
try {
beforeExecute(wt, task);
Throwable thrown = null;
try {
task.run();
} catch (RuntimeException x) {
thrown = x; throw x;
} catch (Error x) {
thrown = x; throw x;
} catch (Throwable x) {
thrown = x; throw new Error(x);
} finally {
afterExecute(task, thrown);
}
} finally {
task = null;
w.completedTasks++;
w.unlock();
}
}
completedAbruptly = false;
} finally {
processWorkerExit(w, completedAbruptly);
}
}
private Runnable getTask() {
boolean timedOut = false; // Did the last poll() time out?
retry:
for (;;) {
int c = ctl.get();
int rs = runStateOf(c);
// Check if queue empty only if necessary.
if (rs >= SHUTDOWN && (rs >= STOP || workQueue.isEmpty())) {
decrementWorkerCount();
return null;
}
boolean timed; // Are workers subject to culling?
for (;;) {
int wc = workerCountOf(c);
timed = allowCoreThreadTimeOut || wc > corePoolSize;
if (wc <= maximumPoolSize && ! (timedOut && timed))
break;
if (compareAndDecrementWorkerCount(c))
return null;
c = ctl.get(); // Re-read ctl
if (runStateOf(c) != rs)
continue retry;
// else CAS failed due to workerCount change; retry inner loop
}
try {
Runnable r = timed ?
workQueue.poll(keepAliveTime, TimeUnit.NANOSECONDS) :
workQueue.take();
if (r != null)
return r;
timedOut = true;
} catch (InterruptedException retry) {
timedOut = false;
}
}
}