Scala futuremap和foreach的行为
我有以下代码,可以在map和future中打印当前线程名Scala futuremap和foreach的行为,scala,Scala,我有以下代码,可以在map和future中打印当前线程名 object ConcurrencyTest1 { def main(args: Array[String]) { import scala.concurrent.ExecutionContext.Implicits.global import scala.concurrent.Future println("main thread: " + Thread.currentThread().getName)
object ConcurrencyTest1 {
def main(args: Array[String]) {
import scala.concurrent.ExecutionContext.Implicits.global
import scala.concurrent.Future
println("main thread: " + Thread.currentThread().getName)
Future {
println("future job: " + Thread.currentThread().getName)
Thread.sleep(1000)
10
}.map { x => {
println("map: " + Thread.currentThread().getName)
Thread.sleep(1000)
x * x
}
}.foreach { x => {
Thread.sleep(1000)
println("foreach: " + Thread.currentThread().getName)
println(x)
}
}
Thread.sleep(5000)
}
}
输出为:
main thread: main
future job: ForkJoinPool-1-worker-5
map: ForkJoinPool-1-worker-5
foreach: ForkJoinPool-1-worker-5
从输出来看,未来的作业、map和foreach都在同一个线程中运行。
我想问这个结果是否是确定性的,也就是说,它总是输出相同的结果。或者,它们可能在不同的线程中运行我认为这并不能保证 然而,在您的例子中,我认为这是从
线程.sleep
调用中得出的(当它们完成时,等待处理的下一个未来是后续的map/foreach;其他未来已经在其他可用线程上启动)
通过删除线程可以看到这一点。sleep
调用:
注意:为了获得更多数据,这将迭代许多参数
运行时:
@ ConcurrencyTestNoSleep.main(Array[String]("a", "b", "c", "d", "e", "f", "g") )
main thread: main
future job a: scala-execution-context-global-954
map a: scala-execution-context-global-954
foreach a:scala-execution-context-global-955
future job c: scala-execution-context-global-955
map c: scala-execution-context-global-955
foreach c:scala-execution-context-global-955
future job d: scala-execution-context-global-955
map d: scala-execution-context-global-955
foreach d:scala-execution-context-global-955
future job e: scala-execution-context-global-955
map e: scala-execution-context-global-955
foreach e:scala-execution-context-global-955
future job f: scala-execution-context-global-955
map f: scala-execution-context-global-955
foreach f:scala-execution-context-global-955
future job g: scala-execution-context-global-955
map g: scala-execution-context-global-955
foreach g:scala-execution-context-global-955
future job b: scala-execution-context-global-954
map b: scala-execution-context-global-954
foreach b:scala-execution-context-global-954
您可以在第三行中看到,“a”
这次运行在两个不同的线程上
但是,在睡眠中,似乎可以重用相同的线程:
object ConcurrencyTestSleep {
def main(args: Array[String]) {
import scala.concurrent.ExecutionContext.Implicits.global
import scala.concurrent.Future
println("main thread: " + Thread.currentThread().getName)
args.map { a =>
Future {
println(s"future job $a: " + Thread.currentThread().getName)
Thread.sleep(1)
10
}.map { x => {
println(s"map $a: " + Thread.currentThread().getName)
Thread.sleep(1)
x * x
}
}.foreach { x => {
Thread.sleep(1)
println(s"foreach $a:" + Thread.currentThread().getName)
// println(x)
}
}
}
Thread.sleep(5000)
}
}
这里,每个参数使用相同的线程(在map和foreach中):
也就是说,我不会依赖这个 我怀疑主要原因是Thread.sleep的时间不准确,这就是为什么在完成上一步后,下一个未来是唯一可用的。谢谢@andy。我在这个问题中循环了200次我的代码,我可以看到结果,它不需要在同一个线程中
object ConcurrencyTestSleep {
def main(args: Array[String]) {
import scala.concurrent.ExecutionContext.Implicits.global
import scala.concurrent.Future
println("main thread: " + Thread.currentThread().getName)
args.map { a =>
Future {
println(s"future job $a: " + Thread.currentThread().getName)
Thread.sleep(1)
10
}.map { x => {
println(s"map $a: " + Thread.currentThread().getName)
Thread.sleep(1)
x * x
}
}.foreach { x => {
Thread.sleep(1)
println(s"foreach $a:" + Thread.currentThread().getName)
// println(x)
}
}
}
Thread.sleep(5000)
}
}
@ ConcurrencyTestSleep.main(Array[String]("a", "b", "c", "d", "e", "f", "g") )
main thread: main
future job a: scala-execution-context-global-1162
map a: scala-execution-context-global-1162
future job c: scala-execution-context-global-1164
future job b: scala-execution-context-global-1163
future job d: scala-execution-context-global-1165
map b: scala-execution-context-global-1163
map c: scala-execution-context-global-1164
map d: scala-execution-context-global-1165
foreach a:scala-execution-context-global-1162
future job e: scala-execution-context-global-1162
foreach b:scala-execution-context-global-1163
foreach d:scala-execution-context-global-1165
future job g: scala-execution-context-global-1165
foreach c:scala-execution-context-global-1164
map e: scala-execution-context-global-1162
future job f: scala-execution-context-global-1163
map g: scala-execution-context-global-1165
map f: scala-execution-context-global-1163
foreach e:scala-execution-context-global-1162
foreach f:scala-execution-context-global-1162
foreach g:scala-execution-context-global-1165