On 07/24/2012 07:15 PM, Christian Thalinger wrote:
>> Not sure if this logic is applicable in this particular case. This is
>> the potential "performance cliff" you are eager to get rid of with new
>> implementation.
> 
> No it's not.  We know exactly what causes the performance cliff.  It's a 
> completely unrelated issue in the VM.

Sorry for misguided definition there, thought quoting does the trick for
me. I was meant to say that the scalability bottlenecks like these pop
out quickly, unexpected and hit hard. The difference between
single-threaded and two-threaded versions could be so dramatic, so you
can easily say it goes down the sink. It's inconvenient to fix one
"cliff" and introduce the other, albeit "completely unrelated".

-Aleksey.

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev

Reply via email to