Hi,
I've been playing around with akka actors to simulate a map-reduce
chain, as mentioned on a former post[1], and I've seen decreased
performance.
Even with work stealing dispatchers.
I was using it in
quite an unusual way, but ended up re-implementing it in Java, and saw
the same pattern.
Is there a example for using akka actors for
increasing perfromance?
Cheers,
- Daniel Ribeiro
[1] http://groups.google.com/group/akka-user/browse_thread/thread/b9d4d7ac537e6582
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
@Viktor
I had mentioned the specifics the linked post (except for machine
stats). But it did not really matter as @Peter Veentjer's suggestion
did the trick. Thanks again for the interest.
@Peter Veentjer
Very nice suggestion. I tried parameterizing grain size (so simple it
didn't even add one line of code), and using coarser grains. Worked
Great. From being slower than the iterative form, it became 30% faster
(needs some fine tuning, of course) in a machine with two cores (and
thanks to workStealer dispatcher).
I am writing a post about akka used in an unconventional way (all the
code in question will be on github shortly), and the performance boost
was just a cherry on top of the ice cream. But a welcomed one.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
Thanks. It was a blast. I've written about my experiences with akka
here: http://bit.ly/g7DDha
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
Thanks. Weird that there's no AOP. It really doesn't work without the
create method on classes.
Guess it would need more akka source
searching to find out the real reason then...
Regards, and keep up the great work.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
Nice write up. I tried doing this with my little project of using
scalaz with futures as it seems like a good, cpu intensive task (at
least once the file is loaded in). I couldn't get jruby working right
on my system to try out your implementation, how many unique words
should be found? This will let me know I'm not doing something wrong.
FYI, I have to increase the work size quite a bit more to reach the
same performance as having dedicated actors (about 10000 lines per
job), so I'm wasting too much CPU time managing actors. When I try
doing 500 line chunks I end up timing out my actors (with a 30 second
timeout set), so good job with that!
--
Derek
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
I did find the issue in my algorithm, I was reducing the wrong way :)
I kept on folding the larger result onto the smaller. Fixed that up
and I've got it running good now. I'm including it as a test on my
akka-scalaz project (http://github.com/derekjw/akka-scalaz).
If you are curious it is the last test in this file:
https://github.com/derekjw/akka-scalaz/blob/master/src/test/scala/FuturesSpec.scala
> --
> You received this message because you are subscribed to the Google Groups "Akka User List" group.
> To post to this group, send email to akka...@googlegroups.com.
> To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
>
>
--
Derek
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
--
Derek
My implementation does run faster, but that has probably more to do
with Scala performing faster then JRuby since I am starting up
thousands of actors instead of just a few, although my reducer doesn't
have to wait for all the mappers to finish before it gets started (the
only await command is for the final result).
Either way it is cool to see Akka used with Ruby. I programmed with
Ruby before switching to Scala about 2 years ago. I had a funny
surprise last week, my copy of the RSpec book from Pragmatic
Programmers finally arrived. Ordered that one over 2 years ago. Yay
early access programs. Kinda useless to me now but maybe it has some
decent stuff on writing good tests. I'm still waiting on my "Merb in
Action" book though... oh wait, it's "Rails 3 in Action" now. Due next
year. Only a little bit later then I expected.
--
Derek
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.