Matthias Ernst wrote: > Charles, > > what do you expect? That the VM spread out all global variables > throughout the heap so that any broken access pattern cause not too > many cache flushes? You're hammering a global from multiple threads, I > don't think you can blame the JVM for that, be it for a new language > or not.
I'm just looking for a definitive answer on why it's better this way in Java 6. If this is a good optimization for other reasons, that's perfectly acceptable and I'll be happy with it. At the moment, however, I have a real-world case where it severely impacted execution performance...so severely that I'd be very surprised if other parts of the system weren't suffering from the same effect. And I'm sure there are other apps out there secretly harboring similar issues. I'm writing up a blog post on this now, so any additional information is very welcome. And I'm not necessarily "blaming" the JVM...but slower is slower. - Charlie --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
