This is a troubleshooting question. I am trying to run the dacapo benchmarks with an older revision (14775) of Jikes, using the ''perf'' test-run (I adapted it to run only the dacapo benchmarks), but the measurements turn out to be very unstable. E. g. for dacapo-fop running the 9 warum-up + 1 timed iterations for 6 executions mostly gives me results within a limited rage (barring 3% of variation), but quite a number of measurements (about one fifth) are very far off (+>10%). I have attempted a small baseline compiler modification to safe some control flow profiling (edge counters); when I run the patched VM with this code, all measurements are catapulted into the higher ballpark.
I have switched off the AOS recompilation, which apparently also ensures that there is no invocation threshold-based recompilation. I am running Ubuntu 7.04 in single user mode on a 2-core Intel machine. The configuration is standard (profiled production build with classpath, dacapo 2006/10). I have not manually started additional system services (not even an Xvfb server to run dacapo-chart) and, as stated above, encounter the phenomenon on the out-of-the-box RVM.
Right now, I am at a loss what might cause these fluctuations, so I am interested in any advice/ideas.
Christian Sinschek,
Technische Universität Darmstadt
--
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen:
http://www.gmx.net/de/go/multimessenger01------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled.
http://p.sf.net/sfu/kodak-com_______________________________________________
Jikesrvm-researchers mailing list
Jikesrvm-researchers@...
https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers
