if you find yourself in this situation managing a lot of Futures, you
might alternatively consider using the 'actor-per-request' pattern:
http://letitcrash.com/post/96078609472/ask-tell-and-per-request-actors
-Michael
On 03/18/15 01:34, Eax Melanhovich wrote:
Lets say we have an actor (#1) which sometimes does `ask` to another
actor (#2). This `ask` returns a Future which may fail if no response
will be received in given timeout (usually 5.seconds). The problem is
that handler of corresponding message in actor #2 creates a lot of
futures connected via flatMap, asks another actors which ask another
actors and so on. What are best practices of finding a real bottleneck
in this case?
Note that actually there could be no single bottleneck if message
handler creates 6 Futures connected via flatMap and each Future takes
1.second to calculate. This case somehow should be recognized too.
--
Read the docs: http://akka.io/docs/
Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
