 |
Martynas Mickevičius |
at Dec 18, 2014 at 2:03 pm
|
⇧ | 
| |
Hi Krishna,
just calling context.actorSelection(...) with a remote path does not hit
network and is naturally latency and bandwidth independent.
Now if you want to get an ActorRef from ActorSelection you need to either
send an Identify message or call resolveOne on ActorSelection. This has a
cost of a message round-trip and is dependent on your network latency.
On Mon, Dec 15, 2014 at 6:58 AM, Krishna Kadam wrote:Hi all,
I am using akka remote actor in my masters project, I have a doubt, I just
want to know, whether the lookup time for an remote actor is dependent on
the speed of network?
or what are the other parameters on which lookup and processing time of
remote actor is dependent?
Thanks
Krishna Kadam
--
http://doc.akka.io/docs/akka/current/additional/faq.html---
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 akka-user+unsubscribe@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at
http://groups.google.com/group/akka-user.For more options, visit
https://groups.google.com/d/optout. --
Martynas Mickevičius
Typesafe <
http://typesafe.com/> – Reactive
<
http://www.reactivemanifesto.org/> Apps on the JVM
--
---
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 akka-user+unsubscribe@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at
http://groups.google.com/group/akka-user.For more options, visit
https://groups.google.com/d/optout.
