Hi Endre
The db calls are Slick 2.x (i.e. blocking) but are within a DbActor with
its own dispatcher. The futures don't have a dedicated dispatcher, but
there shouldn't be anything blocking in the actor that is spawning them.
On Tue, Apr 7, 2015 at 4:21 AM, Akka Team <akka.offic...@gmail.com> wrote:
> Hi Richard,
>
> Are those DB calls async? If so, are they backpressured properly? If not
> (i.e. they are blocking), are they running on a dedicated dispatcher, which
> is not shared with the Futures (i.e. not simply import context.dispatcher
> on actors that do blocking and Futures, but explicitly give a different
> dispatchers to the Futures)?
>
> -Endre
>
> On Fri, Apr 3, 2015 at 9:36 PM, Richard Rodseth <rrods...@gmail.com>
> wrote:
>
>> At startup our application reads a bunch of rows d of type D of a table,
>> and for each sets in motion a bunch of Spray client calls and other
>> database calls then spins up a bunch of actors of type C which generate
>> more HTTP and DB calls. A fair amount of Future composition and pipeTo
>> happens in the course of all this.
>>
>> For larger numbers of Ds (and hence Cs), we are seeing timeouts in the
>> futures (there's not an ask in sight).
>> We haven't done any dispatcher tuning other than giving the DbActor it's
>> own dispatcher because of the blocking.
>>
>> We find ourselves wondering if the "for each d { self ! ProcessD(d)}"
>> should put the Ds on a worker-pull dispatcher, or instead create a
>> per-request ProcessD actor.
>>
>> We've used per-request actors on the API side of the app to eliminate
>> asks and have used the work pulling pattern elsewhere as well.
>>
>> Thoughts?
>>
>>
>> --
>> >>>>>>>>>> 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 akka-user+unsubscr...@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.
>>
>
>
>
> --
> Akka Team
> Typesafe - Reactive apps on the JVM
> Blog: letitcrash.com
> Twitter: @akkateam
>
> --
> >>>>>>>>>> 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 akka-user+unsubscr...@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.
>
--
>>>>>>>>>> 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 akka-user+unsubscr...@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.
