I have actors with round robin pool of size 'n' each . So when app is started I initialize n number of actors in a pool and use them using ActorSystem actorSelection . Question is
1. Do we have to explicitly call context().stop(getSelf()); in each actor after its done doing the work ? As per my understanding if you call .stop() , next time you need an actor and pool actors are all consumed and as long as pool can accommodate creating a new actor it will create a new one and return the instance for processing. with that you would be spending cycles creating an actor and returning (in case of .stop()) vs simply returning from pool (in case of no explicit .stop()) Is my assumption correct ?. 1. Another question is As long as we are using round robin pool (or any other strategy ) there would always be "n" (e.g. 1000) of actors created and if there are more than "n" (e.g 1100) requests at a time , 100 requests are queued in a actors mailbox and processed as actors are freed up ? Can you confirm ? -Thanks R -- >>>>>>>>>> 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 https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
