From 8a47ccf0c637d79453cf9d3852c65965093b3031 Mon Sep 17 00:00:00 2001 From: Derek Mahar Date: Thu, 17 Jan 2013 22:26:06 -0500 Subject: [PATCH] Update akka-docs/rst/general/actor-systems.rst --- akka-docs/rst/general/actor-systems.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/akka-docs/rst/general/actor-systems.rst b/akka-docs/rst/general/actor-systems.rst index 22768a7342..9cd2e2b91f 100644 --- a/akka-docs/rst/general/actor-systems.rst +++ b/akka-docs/rst/general/actor-systems.rst @@ -120,7 +120,7 @@ Examples are legacy RDBMS drivers or messaging APIs, and the underlying reason in typically that (network) I/O occurs under the covers. When facing this, you may be tempted to just wrap the blocking call inside a :class:`Future` and work with that instead, but this strategy is too simple: you are quite likely to -find bottle-necks or run out of memory or threads when the application runs +find bottlenecks or run out of memory or threads when the application runs under increased load. The non-exhaustive list of adequate solutions to the “blocking problem”