聊聊reactive streams的schedulers
序
本文主要研究一下reactive streams的schedulersreact
背景
默认状况下Mono以及Flux都在主线程上运行，有时候可能会阻塞主线程，能够经过设定schedulers让其在其余线程运行。app
原始输出
没有使用publishOn及subscribeOn时输出以下ui
11:26:10.668 [main] DEBUG reactor.util.Loggers$LoggerFactory - Using Slf4j logging framework 11:26:11.097 [main] INFO com.example.demo.SchedulerTest - defer thread:[main] 11:26:11.116 [main] INFO com.example.demo.SchedulerTest - filter thread:[main] 11:26:11.116 [main] INFO com.example.demo.SchedulerTest - filter thread:[main] 11:26:11.116 [main] INFO com.example.demo.SchedulerTest - subscribe thread:[main],data :2 11:26:11.116 [main] INFO com.example.demo.SchedulerTest - filter thread:[main] 11:26:11.116 [main] INFO com.example.demo.SchedulerTest - filter thread:[main] 11:26:11.117 [main] INFO com.example.demo.SchedulerTest - subscribe thread:[main],data :4
publishOn(给subscriber配置线程)
@Test
public void testPublisherThread(){
Scheduler pubScheduler = Schedulers.newSingle("pub-thread");
Flux.defer(() -> {
LOGGER.info("defer thread:[{}]",Thread.currentThread().getName());
return Flux.range(1,4);
})
.filter(e -> {
LOGGER.info("filter thread:[{}]",Thread.currentThread().getName());
return e % 2 == 0;
})
.publishOn(pubScheduler)
.subscribe(e -> {
LOGGER.info("subscribe thread:[{}],data :{}",Thread.currentThread().getName(),e);
});
}
输出线程
11:31:23.691 [main] DEBUG reactor.util.Loggers$LoggerFactory - Using Slf4j logging framework 11:31:23.871 [main] INFO com.example.demo.SchedulerTest - defer thread:[main] 11:31:23.880 [main] INFO com.example.demo.SchedulerTest - filter thread:[main] 11:31:23.881 [main] INFO com.example.demo.SchedulerTest - filter thread:[main] 11:31:23.881 [main] INFO com.example.demo.SchedulerTest - filter thread:[main] 11:31:23.881 [main] INFO com.example.demo.SchedulerTest - filter thread:[main] 11:31:23.881 [publisher-thread-1] INFO com.example.demo.SchedulerTest - subscribe thread:[publisher-thread-1],data :2 11:31:23.881 [publisher-thread-1] INFO com.example.demo.SchedulerTest - subscribe thread:[publisher-thread-1],data :4
能够发现，配置publishOn，改变了subscribe的运行线程
subscribeOn(给publisher配置线程)
@Test
public void testSubscriberThread() throws InterruptedException {
Scheduler subScheduler = Schedulers.newSingle("sub-thread");
Flux.defer(() -> {
LOGGER.info("defer thread:[{}]",Thread.currentThread().getName());
return Flux.range(1,4);
})
.filter(e -> {
LOGGER.info("filter thread:[{}]",Thread.currentThread().getName());
return e % 2 == 0;
})
.subscribeOn(subScheduler)
.subscribe(e -> {
LOGGER.info("subscribe thread:[{}],data :{}",Thread.currentThread().getName(),e);
});
Thread.sleep(10*1000);
}
输出以下：rest
11:31:58.294 [main] DEBUG reactor.util.Loggers$LoggerFactory - Using Slf4j logging framework 11:31:58.528 [subscriber-thread-1] INFO com.example.demo.SchedulerTest - defer thread:[subscriber-thread-1] 11:31:58.532 [subscriber-thread-1] INFO com.example.demo.SchedulerTest - filter thread:[subscriber-thread-1] 11:31:58.532 [subscriber-thread-1] INFO com.example.demo.SchedulerTest - filter thread:[subscriber-thread-1] 11:31:58.532 [subscriber-thread-1] INFO com.example.demo.SchedulerTest - subscribe thread:[subscriber-thread-1],data :2 11:31:58.533 [subscriber-thread-1] INFO com.example.demo.SchedulerTest - filter thread:[subscriber-thread-1] 11:31:58.533 [subscriber-thread-1] INFO com.example.demo.SchedulerTest - filter thread:[subscriber-thread-1] 11:31:58.533 [subscriber-thread-1] INFO com.example.demo.SchedulerTest - subscribe thread:[subscriber-thread-1],data :4
能够发现，配置了subscribeOn，全部的都在这个线程运行，包括defer、包括filter、包括subscribe
publishOn和subscribeOn
@Test
public void testPublisherAndSubscriberThread() throws InterruptedException {
Scheduler pubScheduler = Schedulers.newSingle("publisher-thread");
Scheduler subScheduler = Schedulers.newSingle("subscriber-thread");
Flux.defer(() -> {
LOGGER.info("defer thread:[{}]",Thread.currentThread().getName());
return Flux.range(1,4);
})
.filter(e -> {
LOGGER.info("filter thread:[{}]",Thread.currentThread().getName());
return e % 2 == 0;
})
.publishOn(pubScheduler)
.subscribeOn(subScheduler)
.subscribe(e -> {
LOGGER.info("subscribe thread:[{}],data :{}",Thread.currentThread().getName(),e);
});
Thread.sleep(10*1000);
}
输出code
11:33:00.964 [main] DEBUG reactor.util.Loggers$LoggerFactory - Using Slf4j logging framework 11:33:01.125 [subscriber-thread-1] INFO com.example.demo.SchedulerTest - defer thread:[subscriber-thread-1] 11:33:01.134 [subscriber-thread-1] INFO com.example.demo.SchedulerTest - filter thread:[subscriber-thread-1] 11:33:01.135 [subscriber-thread-1] INFO com.example.demo.SchedulerTest - filter thread:[subscriber-thread-1] 11:33:01.135 [subscriber-thread-1] INFO com.example.demo.SchedulerTest - filter thread:[subscriber-thread-1] 11:33:01.135 [subscriber-thread-1] INFO com.example.demo.SchedulerTest - filter thread:[subscriber-thread-1] 11:33:01.135 [publisher-thread-2] INFO com.example.demo.SchedulerTest - subscribe thread:[publisher-thread-2],data :2 11:33:01.135 [publisher-thread-2] INFO com.example.demo.SchedulerTest - subscribe thread:[publisher-thread-2],data :4
都配置了话，能够看到subscriber运行在publishOn配置的线程，而defer、filter等运行在subscribeOn配置的线程
publishOn及filter
@Test
public void testFilterThread(){
Scheduler pubScheduler = Schedulers.newSingle("publisher-thread");
Flux.defer(() -> {
LOGGER.info("defer thread:[{}]",Thread.currentThread().getName());
return Flux.range(1,4);
})
.publishOn(pubScheduler) //NOTE 注意这里放到了filter以前
.filter(e -> {
LOGGER.info("filter thread:[{}]",Thread.currentThread().getName());
return e % 2 == 0;
})
.subscribe(e -> {
LOGGER.info("subscribe thread:[{}],data :{}",Thread.currentThread().getName(),e);
});
}
输出ip
13:19:01.606 [main] DEBUG reactor.util.Loggers$LoggerFactory - Using Slf4j logging framework 13:19:01.754 [main] INFO com.example.demo.SchedulerTest - defer thread:[main] 13:19:01.766 [publisher-thread-1] INFO com.example.demo.SchedulerTest - filter thread:[publisher-thread-1] 13:19:01.766 [publisher-thread-1] INFO com.example.demo.SchedulerTest - filter thread:[publisher-thread-1] 13:19:01.766 [publisher-thread-1] INFO com.example.demo.SchedulerTest - subscribe thread:[publisher-thread-1],data :2 13:19:01.766 [publisher-thread-1] INFO com.example.demo.SchedulerTest - filter thread:[publisher-thread-1] 13:19:01.766 [publisher-thread-1] INFO com.example.demo.SchedulerTest - filter thread:[publisher-thread-1] 13:19:01.767 [publisher-thread-1] INFO com.example.demo.SchedulerTest - subscribe thread:[publisher-thread-1],data :4
这里将publishOn放在了filter以前，能够发现filter线程也变成publisher线程了
在publishOn以后的filter或map等将使用publishOn配置的线程；以前的话，使用的是main线程或subscribeOn配置的线程
subscribeOn及filter
将subscribeOn放在filter以前，跟以后没有区别，由于没有配置publishOn时，subscribeOn做用于全部，包括filter
window scheduler
还能够给window方法设定线程池get
@Test
public void testWindowScheduler() throws InterruptedException {
Scheduler windowScheduler = Schedulers.newSingle("window-thread");
Flux.defer(() -> {
LOGGER.info("defer thread:[{}]",Thread.currentThread().getName());
return Flux.range(1,4);
})
.delayElements(Duration.ofMillis(200)) //默认会建立parallel线程,做用于subscribe线程
.windowTimeout(1, Duration.ofMillis(100), windowScheduler)
.onErrorReturn(Flux.<Integer>just(-1))
.flatMap(e -> {
return e.map(item -> item*10);
})
.subscribe(e -> {
LOGGER.info("subscribe thread:[{}],data :{}",Thread.currentThread().getName(),e);
});
Thread.sleep(10*1000);
}
输出it
14:15:28.523 [main] DEBUG reactor.util.Loggers$LoggerFactory - Using Slf4j logging framework 14:15:28.701 [main] INFO com.example.demo.SchedulerTest - defer thread:[main] 14:15:28.961 [parallel-1] INFO com.example.demo.SchedulerTest - subscribe thread:[parallel-1],data :10 14:15:29.167 [window-thread-1] INFO com.example.demo.SchedulerTest - subscribe thread:[window-thread-1],data :20 14:15:29.370 [window-thread-1] INFO com.example.demo.SchedulerTest - subscribe thread:[window-thread-1],data :30 14:15:29.573 [parallel-4] INFO com.example.demo.SchedulerTest - subscribe thread:[parallel-4],data :40
注意delayElements方法默认给subscriber建立了parallel线程
timeout()，skip()等方法也默认会建立线程
scheduleGroup
前面在publishOn以及subscribeOn使用的都是Schedulers.newSingle，也能够使用多个线程组成的group，好比io
Scheduler parallelGroup = Schedulers.newParallel("parallel-group", 8);
也能够使用elastic类型，比较适合IO类型的操做
/**
* {@link Scheduler} that dynamically creates ExecutorService-based Workers and caches
* the thread pools, reusing them once the Workers have been shut down.
* <p>
* The maximum number of created thread pools is unbounded.
* <p>
* The default time-to-live for unused thread pools is 60 seconds, use the appropriate
* factory to push a different value.
* <p>
* This scheduler is not restartable.
*
* @param name Thread prefix
*
* @return a new {@link Scheduler} that hosts a fixed pool of single-threaded
* ExecutorService-based workers and is suited for parallel work
*/
public static Scheduler newElastic(String name) {
return newElastic(name, ElasticScheduler.DEFAULT_TTL_SECONDS);
}
实例
@Test
public void testElasticGroup() throws InterruptedException {
Scheduler elastic = Schedulers.newElastic("elastic-group");
Flux.defer(() -> {
LOGGER.info("defer thread:[{}]",Thread.currentThread().getName());
return Flux.range(1,4);
})
.filter(e -> {
LOGGER.info("filter thread:[{}]",Thread.currentThread().getName());
return e % 2 == 0;
})
.publishOn(elastic)
.map(e -> {
LOGGER.info("map thread:[{}]",Thread.currentThread().getName());
return e * 10;
})
.subscribeOn(elastic)
.subscribe(e -> {
LOGGER.info("subscribe thread:[{}],data :{}",Thread.currentThread().getName(),e);
});
Thread.sleep(10*1000);
}
输出
13:58:37.356 [main] DEBUG reactor.util.Loggers$LoggerFactory - Using Slf4j logging framework 13:58:37.514 [elastic-group-2] INFO com.example.demo.SchedulerTest - defer thread:[elastic-group-2] 13:58:37.520 [elastic-group-2] INFO com.example.demo.SchedulerTest - filter thread:[elastic-group-2] 13:58:37.520 [elastic-group-2] INFO com.example.demo.SchedulerTest - filter thread:[elastic-group-2] 13:58:37.520 [elastic-group-2] INFO com.example.demo.SchedulerTest - filter thread:[elastic-group-2] 13:58:37.520 [elastic-group-2] INFO com.example.demo.SchedulerTest - filter thread:[elastic-group-2] 13:58:37.520 [elastic-group-3] INFO com.example.demo.SchedulerTest - map thread:[elastic-group-3] 13:58:37.520 [elastic-group-3] INFO com.example.demo.SchedulerTest - subscribe thread:[elastic-group-3],data :20 13:58:37.521 [elastic-group-3] INFO com.example.demo.SchedulerTest - map thread:[elastic-group-3] 13:58:37.521 [elastic-group-3] INFO com.example.demo.SchedulerTest - subscribe thread:[elastic-group-3],data :40
小结
- 命名
这个publishOn及subscribeOn方法名有点晦涩，更直白一点至关于subscriberThreadPools以及publisherThreadPools。
- publishOn与operations的位置
在publishOn以后的filter或map等将使用publishOn配置的线程；以前的话，使用的是main线程或subscribeOn配置的线程
- subscribeOn
在没有配置publishOn，只配置subscribeOn的话，则做用全部
- 方法内置线程
delayElements(),timeout(),skip()内置会使用额外的线程
doc
相关文章
- 1. 聊聊reactive streams的processors
- 2. 聊聊reactive streams的parallel flux
- 3. 聊聊reactive streams的backpressure
- 4. 聊聊reactive streams的Mono及Flux
- 5. 聊聊reactive streams publisher的doOn方法
- 6. 聊聊reactive streams的tranform操做
- 7. Spring Boot Reactive Streams
- 8. Java 9 Reactive Streams
- 9. java9之Reactive Streams
- 10. What can Reactive Streams offer EE4J?
- 更多相关文章...
- • PHP imagecolorclosest - 取得与指定的颜色最接近的颜色的索引值 - PHP参考手册
- • PHP imagecolorclosesthwb - 取得与指定的颜色最接近的色度的黑白色的索引 - PHP参考手册
- • 漫谈MySQL的锁机制
- • 互联网组织的未来：剖析GitHub员工的任性之源
相关标签/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
最新文章
- 1. 跳槽面试的几个实用小技巧，不妨看看！
- 2. Mac实用技巧 |如何使用Mac系统中自带的预览工具将图片变成黑白色?
- 3. Mac实用技巧 |如何使用Mac系统中自带的预览工具将图片变成黑白色?
- 4. 如何使用Mac系统中自带的预览工具将图片变成黑白色?
- 5. Mac OS非兼容Windows软件运行解决方案——“以VMware & Microsoft Access为例“
- 6. 封装 pyinstaller -F -i b.ico excel.py
- 7. 数据库作业三ER图待完善
- 8. nvm安装使用低版本node.js(非命令安装)
- 9. 如何快速转换图片格式
- 10. 将表格内容分条转换为若干文档
欢迎关注本站公众号,获取更多信息
相关文章
- 1. 聊聊reactive streams的processors
- 2. 聊聊reactive streams的parallel flux
- 3. 聊聊reactive streams的backpressure
- 4. 聊聊reactive streams的Mono及Flux
- 5. 聊聊reactive streams publisher的doOn方法
- 6. 聊聊reactive streams的tranform操做
- 7. Spring Boot Reactive Streams
- 8. Java 9 Reactive Streams
- 9. java9之Reactive Streams
- 10. What can Reactive Streams offer EE4J?