Charles Oliver Nutter schrieb: > I ran into a very strange effect when some Sun folks tried to benchmark > JRuby's multi-thread scalability. In short, adding more threads actually > caused the benchmarks to take longer. [...] > Instead pay attention to the trend...the soylatte Java > 6 run with two threads is significantly slower than the run with a > single thread. This mirrors the results with JRuby when there was a > single static counter being incremented.
I think there is not enough data to see a trend. I modified your test, made it run from 1-20 threads and for 50 loops, making an average time containing the time it took to execute all threads and put these in a diagram. I used a Q6600 Quadcore intel CPU with java 1.6.0_03-b05 on Linux 2.6.22-14-generic #1 SMP x86_64 GNU/Linux. What I can see is that the time constantly goes up until 4 Threads are reached, my number of CPUs. Using 5 threads is takes less time than using 4, but after that the time looks more or less constant. This looks quite scalable to me. bye blackdrag -- Jochen "blackdrag" Theodorou The Groovy Project Tech Lead (http://groovy.codehaus.org) http://blackdragsview.blogspot.com/ http://www.g2one.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
