Futures for blocking calls in Scala

Question

The Akka documentation says:

you may be tempted to just wrap the blocking call inside a Future and work with that instead, but this strategy is too simple: you are quite likely to find bottlenecks or run out of memory or threads when the application runs under increased load.

They suggest the following strategies:

Do the blocking call within a Future, ensuring an upper bound on the number of such calls at any point in time (submitting an unbounded number of tasks of this nature will exhaust your memory or thread limits).
Do the blocking call within a Future, providing a thread pool with an upper limit on the number of threads which is appropriate for the hardware on which the application runs.

Do you know about any implementation of those strategies?

Marius Danila · Accepted Answer · 2014-08-05T14:53:40.087

17

Futures are run within execution contexts. This is obvious from the Future API: any call which involves attaching some callbacks to a future or to build a future from an arbitrary computation or from another future requires an implicitly available ExecutionContext object. So you can control the concurrency setup for your futures by tuning the ExecutionContext in which they run.

For instance, to implement the second strategy you can do something like

import scala.concurrent.ExecutionContext
import java.util.concurrent.Executors
import scala.concurrent.future

object Main extends App {

  val ThreadCount = 10
  implicit val executionContext = ExecutionContext.fromExecutor(Executors.newFixedThreadPool(ThreadCount))

  val f = future {
    println(s"Hello ! I'm running in an execution context with $ThreadCount threads")
  }

}

edited Aug 05 '14 at 14:53

answered Apr 11 '13 at 14:21

Marius Danila

10,311
2
34
37

Thanks but it looks too Java. I am looking for more "Scala-ish" approach. – Michael Apr 11 '13 at 15:24
7

Well, I don't think it gets more Scala-ish than the `scala.concurrent` library. – Marius Danila Apr 11 '13 at 15:48
Also, it doesn't get any more "Scala-ish" than http://www.scala-lang.org/files/archive/nightly/docs/library/index.html#scala.concurrent.ExecutionContext – axiopisty May 29 '14 at 15:51

score 2 · Answer 2 · answered Apr 11 '13 at 14:21

2

Akka itself implements all this, you can wrap your blocking calls into Actors and then use dispatchers to control execution thread pools.

answered Apr 11 '13 at 14:21

themel

8,825
2
32
31

To add to this, please refrain from using an ActorSystem's default dispatcher for executing Futures that contain blocking calls, as doing so will create a bottleneck for the Actor instances. It's better to allocate a separate ExecutionContext dedicated for executing these blocking codes. – lolski Jun 23 '15 at 08:35

Futures for blocking calls in Scala

2 Answers2

Linked