On Apr 2, 2008, at 4:01 AM, John Wilson wrote: > I'm just wondering if this might be some issue with the cache on Intel > mutli core processors (i.e. the cache is constantly being > invalidated).
Yes, that code will in general cause cache ping-ponging, which in the long run will harm sharing and hence scalability. On a single socket system, the sharing ought to be pretty good, though. And that doesn't explain the difference between 5 and 6. This looks like a question for the hotspot-runtime-dev list. http://mail.openjdk.java.net/mailman/listinfo/hotspot-runtime-dev -- John P.S. Today I'm pushing the disassembler plugin for Hotspot 13, to come out with the first flood of pending OpenJDK changes, RSN. It will support disassembly of code even on product versions of Hotspot, making it *much* easier to discuss issues like this. Webrev (slightly out-of-date) is here: http://webrev.invokedynamic.info/jrose/6667042/ The only current implementation of the disassembler uses Gnu binutils. We don't link Gnu code into Hotspot, but this isn't a problem, since the disassembler is loaded into the JVM as a plugin. The downside is you'll have to build the disassembler plugin yourself. There are build instructions (using Gnu binutils) in the Hotspot sources. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to jvm-languages@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
