Any major performance change with I/O from JDK 6 that one should be aware of?
Fabrizio Giudici
Fabrizio.Giudici at tidalwave.it
Mon May 14 05:17:52 PDT 2012
On Mon, 14 May 2012 13:29:59 +0200, Tomas Hurka
<tomas.hurka at googlemail.com> wrote:
>> option that can be used as well?
> Use -XX:CompileCommand. See
> <http://cleversoft.wordpress.com/2010/07/21/xxcompilecommandexclude-jvm-option/>
> for more details.
Thanks. So, I'm trying it with the whole application and I'm seeing again
the original performance :-) (actually still a bit lower, but I'm doing
this in parallel with other stuff, I need to re-run the tests without
other processes in background - in any case it's not 10x slower as
previously). In any case, it seems that this confirms the explanation in
my previous message, that if load() doesn't pre-load everything in memory
(and it's efficient), the MD5 method accesses data in a way that it
doesn't load them in an efficient way.
Very subtle!
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
fabrizio.giudici at tidalwave.it
http://tidalwave.it - http://fabriziogiudici.it
More information about the macosx-port-dev
mailing list