线程池源码解析
线程池的优势
当一个业务处理时间短,但是需要频繁处理的时候,可以进行线程池的创建,避免大量创建线程浪费资源。在创建线程时,需要通过start0()方法调用底层的系统资源,往往这个操作是一个很重的操作,那么创建线程池,可以保留几个核心线程,使用take()方法让它处于阻塞状态,当需要使用线程时,将任务放入队列中,队列中的任务就可以激活阻塞线程进行执行,这个激活的状态处于用户态,可以避免线程的创建。
线程池参数说明
public ThreadPoolExecutor(int corePoolSize,
int maximumPoolSize,
long keepAliveTime,
TimeUnit unit,
BlockingQueue<Runnable> workQueue)
corePoolSize:核心线程数量,在空闲期间也不会销毁
maximumPoolSize:最大线程数量,在空闲期间会被销毁,销毁数量为:maximumPoolSize-corePoolSize
keepAliveTime:空闲非核心线程存活时间
unit: 存活时间单位
workQueue:当任务量大于最大线程数量时,将任务存储到队列中,这边可以选择采用那种队列:
- ArrayBlockingQueue:基于数组结构的有界阻塞队列;
- LinkedBlockingQuene:基于链表结构的有界阻塞队列;
- SynchronousQuene:不存储元素的阻塞队列,每插入一个元素就需要一个线程来执行,相当于中转站;
- PriorityBlockingQuene:支持线程优先级排序的无界阻塞队列;
ThreadPoolExecutor源码解析基础参数说明:
//原子类 1.高三位是当前线程池的状态 2.后29位是线程池中的线程数
private final AtomicInteger ctl = new AtomicInteger(ctlOf(RUNNING, 0));
//方便后续做位运算,获取29个字节
private static final int COUNT_BITS = Integer.SIZE - 3;
//线程池中线程的最大数量2^29-1
private static final int CAPACITY = (1 << COUNT_BITS) - 1;
//RUNNING(运行状态) < SHUTDOWN(准备关闭状态,不接受新任务,但执行队列任务) < STOP(暂停状态,不接受新任务,不执行队列任务) < TIDYING(过渡状态) < TERMINATED(关闭状态)
// runState is stored in the high-order bits
//-1(11111111111111111111111111111111)往后移动29位移 ,running值为 11100000000000000000000000000000(前三位:111)
private static final int RUNNING = -1 << COUNT_BITS;
//0(00000000000000000000000000000000)往后移动29位移 ,SHUTDOWN值为 00000000000000000000000000000000(前三位:000)
private static final int SHUTDOWN = 0 << COUNT_BITS;
//1(00000000000000000000000000000001)往后移动29位移 , STOP值为 00010000000000000000000000000000(前三位:001)
private static final int STOP = 1 << COUNT_BITS;
//2(00000000000000000000000000000010)往后移动29位移 , TIDYING值为 00100000000000000000000000000000(前三位:010)
private static final int TIDYING = 2 << COUNT_BITS;
//3(00000000000000000000000000000011)往后移动29位移 ,TERMINATED值为 01100000000000000000000000000000(前三位:011)
private static final int TERMINATED = 3 << COUNT_BITS;
// Packing and unpacking ctl
//获取运行状态
private static int runStateOf(int c) { return c & ~CAPACITY; }
//取低29位,获取当前活跃线程
private static int workerCountOf(int c) { return c & CAPACITY; }
//计算ctl值,高3位线程池状态+低29位线程池数量
private static int ctlOf(int rs, int wc) { return rs | wc; }
线程池状态说明:
执行线程:execute()
public void execute(Runnable command) {
//判断线程是否未null
if (command == null)
throw new NullPointerException();
//获取线程池——》高三位(状态),后29位(数量)
int c = ctl.get();
//判断如果工作线程数量<核心线程数量
if (workerCountOf(c) < corePoolSize) {
//启动工作线程,true进行核心线程池校验,false进行最大线程池校验
if (addWorker(command, true))
return;
//进行核心线程池添加失败,重新获取线程状态
c = ctl.get();
}
//判断线程是否处于运行状态,并且将线程添加到队列中
if (isRunning(c) && workQueue.offer(command)) {
//再次重新获取线程状态校验目前线程池情况
int recheck = ctl.get();
//如果线程池不处于运行状态,将线程移除队列并调用拒绝策略
if (! isRunning(recheck) && remove(command))
reject(command);
//判断工作线程个数,如果为0,添加工作线程
else if (workerCountOf(recheck) == 0)
addWorker(null, false);
}
//如果线程池添加队列失败,调用拒绝策略
else if (!addWorker(command, false))
reject(command);
}
添加woker:addWorker()
private boolean addWorker(Runnable firstTask, boolean core) {
//标记双重循环break之后,退出到标记点
retry:
for (;;) {
//获取线程状态,数量
int c = ctl.get();
//获取线程运行状态
int rs = runStateOf(c);
// Check if queue empty only if necessary.
//如果线程>=SHUTDOWN,并且rs不等于SHUTDOWN,firstTask任务不为空,队列为空时直接返回false
if (rs >= SHUTDOWN &&
! (rs == SHUTDOWN &&
firstTask == null &&
! workQueue.isEmpty()))
return false;
for (;;) {
//获取工作线程数量
int wc = workerCountOf(c);
//如果wc>=最大可创建线程数量或者 core-》如果为true拿核心线程数,如果为false拿最大线程数,
if (wc >= CAPACITY ||
wc >= (core ? corePoolSize : maximumPoolSize))
return false;
//cas修改工作线程数量,修改成功返回到标记点retry
if (compareAndIncrementWorkerCount(c))
break retry;
//如果没修改成功,表示存在竞争,重新拿到线程池状态进行循环
c = ctl.get(); // Re-read ctl
//如果拿到的当前线程池状态和开始循环的线程池状态不同则跳出retry
if (runStateOf(c) != rs)
continue retry;
// else CAS failed due to workerCount change; retry inner loop
}
}
//
boolean workerStarted = false;
boolean workerAdded = false;
java.util.concurrent.ThreadPoolExecutor.Worker w = null;
try {
//将任务添加到worker中
w = new java.util.concurrent.ThreadPoolExecutor.Worker(firstTask);
//获取worker的线程
final Thread t = w.thread;
if (t != null) {
//线程池加锁,开始执行任务
final ReentrantLock mainLock = this.mainLock;
mainLock.lock();
try {
//获取当前线程池运行状态
int rs = runStateOf(ctl.get());
//如果rs<SHUTDOWN 或者 (rs== SHUTDOWN 并且 firstTask任务为空)
if (rs < SHUTDOWN ||
(rs == SHUTDOWN && firstTask == null)) {
//t任务是否启动
if (t.isAlive()) // precheck that t is startable
throw new IllegalThreadStateException();
//将worker添加到workers中
workers.add(w);
int s = workers.size();
//如果workers大于以前的线程池数量,则进行赋值
if (s > largestPoolSize)
largestPoolSize = s;
workerAdded = true;
}
} finally {
mainLock.unlock();
}
//添加完成,启动worker中的run,也就是runWorker
if (workerAdded) {
t.start();
workerStarted = true;
}
}
} finally {
//如果未调用t线程,则添加任务失败,删除该任务并且cas还原以前的线程池数量
if (! workerStarted)
addWorkerFailed(w);
}
return workerStarted;
}
启动worker:runWorker()
final void runWorker(java.util.concurrent.ThreadPoolExecutor.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线程,如果线程池是停止状态,wt不为中断也字段wt线程
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);
}
}
获取队列中的任务:getTask()
private Runnable getTask() {
boolean timedOut = false; // Did the last poll() time out?
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;
}
int wc = workerCountOf(c);
// Are workers subject to culling?
boolean timed = allowCoreThreadTimeOut || wc > corePoolSize;
if ((wc > maximumPoolSize || (timed && timedOut))
&& (wc > 1 || workQueue.isEmpty())) {
if (compareAndDecrementWorkerCount(c))
return null;
continue;
}
try {
//获取线程任务或者阻塞线程池
Runnable r = timed ?
workQueue.poll(keepAliveTime, TimeUnit.NANOSECONDS) :
workQueue.take();
if (r != null)
return r;
timedOut = true;
} catch (InterruptedException retry) {
timedOut = false;
}
}
}
其它总结
核心线程(Worker)一直空闲也不终止,因为通过workQueue.take()实现的,它会一直阻塞到从等待队列中取到新的任务。非核心线程空闲指定时间后终止是通过workQueue.poll(keepAliveTime, TimeUnit.NANOSECONDS)实现的,一个空闲的Worker只等待keepAliveTime,如果没有获取到任务则循环终止,线程也就运行结束了。