Thank you Konrad for really fast response! I read the docs again and if I correct understood my configuration can/should be like this one: *1. Dispatcher(s)* One dispatcher for all web service clients with fixed size. Size of the pool correspond to CPU amount (16 for 16 cores) *or* dispatcher pro web service client with fixed size. Size of the pool = number of cores / dispatcher amount
*Question:* - does it make really sense to create dispatcher pro web service client or one for all? Do you've any experience with it? - is it better to use Dispatcher with fork-join or fixed-size one? *2. Connection pool(s)* Currently I use one *cachedHostConnectionPool* connection pool for all materializations for given host/port. I use also *Source.queue *to handle more requests, if necessary. Size of pool is of course very specific to the running environment - I set max to 256. *Questions:* - how "heavy" is queuing? Are "just" request objects kept in queue? - theoretically if connection pool is bigger then dispatcher threads should be also bigger -> to handle responses fast enough. In other words, make it sense to limit connection pool if dispatcher has less threads? Am I right / make it sense? Cheers, Albert -- >>>>>>>>>> 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.
