今天测试了一下++这种自增方式是不是线程安全的。于是写了如下demo:
package com.meiran;
import org.junit.Test;
import java.util.concurrent.CountDownLatch;
import java.util.concurrent.atomic.AtomicInteger;
/**
* 原子类测试
*
* @date 2016/8/22
*/
public class AtomicIntegerTest {
private AtomicInteger calsign = new AtomicInteger(0);
// private Integer calsign = 0;
private CountDownLatch countDownLatch = new CountDownLatch(20);
/**
* 测试i++不是原子操作
*/
@Test
public void test() {
for (int i = 0; i < 20; i++) {
//开启50个线程
Thread t = new Thread(new Runnable() {
@Override
public void run() {
for (int i = 0; i < 10000; i++) {
calsign.incrementAndGet();
// calsign++;
}
//计算器减一
countDownLatch.countDown();
}
});
t.start();
}
try {
//当计算器减到0,继续执行。目的是等待所有线程均结束
countDownLatch.await();
} catch (InterruptedException e) {
e.printStackTrace();
}
System.out.println(calsign);
}
}
如果用原子类,结果总输出:200000
但是如果用calsign++,结果输出的值总是小于200000。原因是因为在高并发时,自增后的值有可能在另一个线程中是未自增的,于是造成覆盖。