Ouch. So what doe Akka muster on your machine with the same-ish type of config?
On Wed, Jan 15, 2014 at 11:32 AM, Roger Alsing <[email protected]>wrote: > The .NET thread pool does some magic with the threads, I'm not sure what > state those threads are in by default or if they even are alive at all. > But the threadpool does measure how long each job takes and how much is > scheduled on the queue, and decide how many threads to use from that. > > >>So if you only use 4 OS-threads in your ThreadPool, and use 8 actors, > you get ~4779000? > Yes > > > > Den onsdagen den 15:e januari 2014 kl. 11:20:12 UTC+1 skrev √: > >> >> >> >> On Wed, Jan 15, 2014 at 11:16 AM, Roger Alsing <[email protected]>wrote: >> >>> On my machine I get the best throughput with only 4 actors and I guess >>> that maps to my 4 cores. >>> Scheduling in the .NET thread pool seems pretty darn expensive even >>> though it is lock-less, the more actors I add after this, the throughput >>> drops considerably. >>> The threadpool defaults to 1023 worker threads, but I can get the same >>> result using only 3 threads in the pool. >>> >> >> What?! 1023 OS-threads?! >> >> >>> >>> But as you can see, it goes downhill quite fast after the peak. so I >>> need to do something about the scheduler.. >>> >>> Actors count, messages/s: >>> >>> 2, 4732000 messages/s >>> 4, 8944000 messages/s >>> 6, 6664000 messages/s >>> 8, 4779000 messages/s >>> >> >> So if you only use 4 OS-threads in your ThreadPool, and use 8 actors, you >> get ~4779000? >> >> Cheers, >> √ >> >> >>> >>> >>> >>> >>> Den onsdagen den 15:e januari 2014 kl. 10:54:25 UTC+1 skrev √: >>> >>>> >>>> >>>> >>>> On Wed, Jan 15, 2014 at 10:40 AM, Roger Alsing <[email protected]>wrote: >>>> >>>>> I couldn't find much else than that the Java ThreadPool does >>>>> locking/blocking when scheduling, I guess that is the main reason? >>>>> And that the new modified fork join pool does random scheduling and >>>>> work stealing (?) >>>>> It turns out that the .NET ThreadPool is non locking and also does job >>>>> stealing, so I guess I'll stick to that implementation for now. >>>>> >>>>> Processing 8.5 mil messages/sec on my 4 core 2.8 ghz laptop using a >>>>> ported version of your ping pong client actors. >>>>> >>>> >>>> With how many actors and how many threads? >>>> >>>> >>>>> I guess that is a pretty decent number considering that Akka pushed 20 >>>>> mil/sec on that 48 core server using the first fork join implementation >>>>> (?) >>>>> >>>> >>>> 48-core server is actually a worsening factor in this case. >>>> >>>> Cheers, >>>> √ >>>> >>>> >>>>> >>>>> >>>>> Den måndagen den 13:e januari 2014 kl. 13:01:02 UTC+1 skrev √: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Mon, Jan 13, 2014 at 11:52 AM, Roger Alsing <[email protected]>wrote: >>>>>> >>>>>>> I'm trying to understand why the fork join pool scales better than >>>>>>> the thread pool. >>>>>>> >>>>>> >>>>>> LMGTFY? :) >>>>>> >>>>>> https://www.google.com/search?q=akka+scale+ForkJoinPool&oq=a >>>>>> kka+scale+ForkJoinPool >>>>>> >>>>>> >>>>>>> My understanding is that FJP can partition tasks into subtasks to >>>>>>> optimize the work done on the underlying threads. >>>>>>> >>>>>>> How does this affect the mailboxes in Akka? >>>>>>> Since a given mailbox can only process one message at a time to >>>>>>> ensure max degree of paralellism = 1 for the actor model, I fail to see >>>>>>> how >>>>>>> the FJP model helps here? >>>>>>> >>>>>>> Is it just that registerForExecution is faster with fjp than >>>>>>> treadpool? >>>>>>> >>>>>> >>>>>> Let's talk after you read the blog post! >>>>>> >>>>>> Cheers, >>>>>> √ >>>>>> >>>>>> >>>>>>> -- >>>>>>> >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>> >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>> >>>>>>>>>> Search the archives: https://groups.google.com/grou >>>>>>> p/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/groups/opt_out. >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Cheers, >>>>>> √ >>>>>> >>>>>> * Viktor Klang* >>>>>> *Director of Engineering* >>>>>> Typesafe <http://www.typesafe.com/> >>>>>> >>>>>> Twitter: @viktorklang >>>>>> >>>>> -- >>>>> >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>> >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>> >>>>>>>>>> Search the archives: https://groups.google.com/grou >>>>> p/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/groups/opt_out. >>>>> >>>> >>>> >>>> >>>> -- >>>> Cheers, >>>> √ >>>> >>>> * Viktor Klang* >>>> *Director of Engineering* >>>> Typesafe <http://www.typesafe.com/> >>>> >>>> Twitter: @viktorklang >>>> >>> -- >>> >>>>>>>>>> Read the docs: http://akka.io/docs/ >>> >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>> >>>>>>>>>> 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/groups/opt_out. >>> >> >> >> >> -- >> Cheers, >> √ >> >> * Viktor Klang* >> *Director of Engineering* >> Typesafe <http://www.typesafe.com/> >> >> Twitter: @viktorklang >> > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ > >>>>>>>>>> Check the FAQ: http://akka.io/faq/ > >>>>>>>>>> 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/groups/opt_out. > -- Cheers, √ *Viktor Klang* *Director of Engineering* Typesafe <http://www.typesafe.com/> Twitter: @viktorklang -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> 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/groups/opt_out.
