Yes i posted the 100 iterations with 1million messages on imgur. The samples are with 1000 iterations per job and 100k jobs. Unfortunately i cannot access google docs from work .. i have the same chart for the 1000/100k version you are running
Just change the constants at the top/bottom of the snippets. Am Dienstag, 7. Januar 2014 17:40:44 UTC+1 schrieb Alec Zorab: > > I can't see your imgur results from the office, but when I run your two > gists on my workstation I get results like this - do yours differ > significantly from mine? > > akka: > Pi approximation: 3.1415926435898274 Calculation time: 244 > average 1 threads : 767 > average 2 threads : 396 > average 3 threads : 303 > average 4 threads : 259 > average 5 threads : 227 > average 6 threads : 205 > average 7 threads : 188 > average 8 threads : 187 > average 9 threads : 222 > average 10 threads : 218 > average 11 threads : 210 > average 12 threads : 208 > average 13 threads : 205 > average 14 threads : 208 > average 15 threads : 209 > average 16 threads : 205 > > ThreadPi: > average 1 threads : 720 > average 2 threads : 383 > average 3 threads : 278 > average 4 threads : 210 > average 5 threads : 198 > average 6 threads : 189 > average 7 threads : 184 > average 8 threads : 167 > average 9 threads : 186 > average 10 threads : 184 > average 11 threads : 186 > average 12 threads : 183 > average 13 threads : 189 > average 14 threads : 185 > average 15 threads : 186 > average 16 threads : 187 > > > > > On 7 January 2014 16:26, Rüdiger Möller <[email protected] > <javascript:>>wrote: > >> >>> I'm not sure a hand-wavy reference to Cliff is going to quench my thirst >>> for facts even though Cliff is a great guy. >>> >> >> I googled that for you: >> A JVM Does That? - YouTube <http://www.youtube.com/watch?v=uL2D3qzHtqY> >> >> Again: your obsession with time measurement makes sense when measuring >> small amounts of ticks and adding them up, but not in the context of a >> longer running test. You easily may copy the snippet and add nanotime >> measurement. It will not make significant difference. >> >> >> >>> >>>> >>>> >>>> >>>>> >>>>>>> https://github.com/viktorklang/scala-vs-erlang/blob/9a124c75 >>>>>>> c8034d9ba90baa2751f21c51f1e64ddc/scala/src/main/resources/ap >>>>>>> plication.conf >>>>>>> >>>>>> >>>>> Did you apply this? >>>>> >>>>> >>>> >>>> No, but i will try. I am not interested in presenting skewed >>>> benchmarks. Abstraktor is not a competing project, its just my playground >>>> lean actor impl to get a raw feeling of what should be possible. >>>> >>> >>> The default settings is definitely not optimal for your use-case (as >>> default settings rarely are). >>> >> >> That's why I preferred talking back here :-) >> >> >>> >>> >>>> >>>> | Single-machine performance is only interesting if you are after >>>> single points of failure. >>>> >>>> Both things are important: single machine performance AND remote >>>> messaging throughput + latency. >>>> >>> >>> Yep, my argument was that without remote you have a spof. >>> >>> >>>> Regarding remoting/failover there are much faster options than >>>> actors/Akka today. >>>> >>> >>> Reference? >>> >> >> thinking of IBM WLLM or Informatika UM. Does Akka offer reliable UDP >> messaging with several million msg/sec througput, from what I have seen its >> challenging enough to get this on localhost. I have used the former, its >> really blasting fast (at elast with kernel bypass networking equipment). >> >> >>> >>> >>>> I appreciate your vision of making this transparent to the application. >>>> Its a great idea, but I think your are still not there for the very high >>>> end kind of application, no offence. I have built large high performance >>>> distributed systems, so I know what I am talking bout. >>>> >>> >>> What are you basing this opinion on, and what benchmark/setting are you >>> comparing? >>> >> >> Benchmarks and some public bragging with not-so-impressive numbers .. >> ;-). Also i can see in single threaded benchmarks, Akka's message passing >> adds significant overhead compared to single threaded executor and >> byte-weaving based proxying as used in other libs. One even can do remote >> messaging faster than Akka does inter thread messaging, so there definitely >> is room for improvement. Does Akka provide reliable UDP messaging (NAK >> based, not acknowledged ?). That's what you need for high end >> throughput+failover imo. Doing typed actor message passing via JDK proxies >> e.g. is well .. you should know yourself :-) >> >> >>> >>> >>>> However regarding concurrent programming, actors can improve >>>> performance and maintainability today, that's why i am currently >>>> investigating/benchmarking local performance only. >>>> I'll will incorporate your proposals into the test. >>>> >>> >>> Great, let us know what the results were. >>> >> >> Don't expect too much, as I pointed out from my POV the problem is >> already inside Akkas basic message passing performance IMO, so Akka has a >> hard time breaking even when scaling. We'll see. >> >> >>> >>> Cheers, >>> √ >>> >>> >>>> >>>> regards, >>>> Rüdiger >>>> >>>> -- >>>> >>>>>>>>>> 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] <javascript:>. >> To post to this group, send email to [email protected]<javascript:> >> . >> Visit this group at http://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- >>>>>>>>>> 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.
