DaCapo 9.10-beta0 available

2009-09-11 Thread Steve Blackburn
We are pleased to announce the beta release of the forthcoming major  
release of the DaCapo benchmark suite.   We apologize if you receive  
this email more than once.


Please note that this BETA release is NOT SUITABLE AS A RESEARCH  
TOOL.  The purpose of the release is to invite researchers  
(particularly JVM developers) to evaluate the it and give us feedback  
(see links below for mailing list and bug trackers).   Please be sure  
to note known bugs and limitations (see end of release notes) before  
sending in feedback.


This will be the first of a number of beta releases.   Please check  
the web site for updates.


We welcome your feedback and thank many of you for the contributions  
you've made already.


Best wishes,

Steve Blackburn, ANU
John Zigman, ANU
Kathryn McKinley, UT Austin
(On behalf of the DaCapo project).


-
Key information:

1.  Source and binary downloads are available here:

https://sourceforge.net/projects/dacapobench/files/dacapobench/9.10-beta0
2.  Release notes are available below and here:
http://www.dacapo-bench.org/RELEASE_NOTES.txt
3.  Bug tracker and feature requests here:
http://sourceforge.net/projects/dacapobench/develop
http://sourceforge.net/tracker/?group_id=172498atid=861957
http://sourceforge.net/tracker/?group_id=172498atid=861960
4.  Mailing list here:
https://sourceforge.net/mail/?group_id=172498
5.  Regression results here:
http://dacapo.anu.edu.au/regression/sanity/latest/index.html
http://dacapo.anu.edu.au/regression/perf/head.html

-

dacapo-9.10-beta0

RELEASE NOTES  2009-09-10


* IMPORTANT: This beta release is NOT SUITABLE AS A RESEARCH TOOL. *
*  *
* Please wait for the full release before using the suite for research *
* purposes. The benchmarks in this beta release are:   *
*  *
*1) not fully tuned,   *
*2) not fully evaluated,   *
*3) known to have various limitations and bugs, and*
*4) subject to change without notice.  *
*  *



This is the first beta release of the anticipated 9.10 release of the
DaCapo benchmark suite.  These notes are structured as follows:

1. Purpose
2. Overview
3. Usage
4. Changes
5. Known problems and limitations



1. Purpose
--

This beta release exists specifically (and only) to allow community
feedback and contribution to the upcoming major release, and to allow
JVM vendors to test against the suite prior to the final release. We
strongly encourage the community to explore and evaluate these
benchmarks and to send feedback to the dacapo research group via the
mailing list and/or bug tracker. Please check the list of known issues
(below) before sending feedback.


   mailing list: dacapobench-research...@lists.sourceforge.net
 (subscribe via: http://sourceforge.net/mail/?group_id=172498)

   bug tracker:
   http://sourceforge.net/tracker/?group_id=172498atid=861957
 or navigate to it from
   http://sourceforge.net/projects/dacapobench/develop


We are particularly interested in feedback on the following:

o The decision to add benchmarks avrora, batik, derby,
  sunflow, tomcat, tradebeans, and tradesoap (see 4.1
  below).

o The decision to retire benchmarks antlr, bloat, chart,
  and hsqldb (see 4.2 below).

o The tuning / running time of each of the benchmarks in their
  default settings.

o The structure and behavior of the tradebeans, tradesoap and
  tomcat client/server benchmarks.

o Any issues associated with building, running and usability of
  the suite.


2. Overview
---

The DaCapo benchmark suite is slated to be updated every few years.
The 9.10 release will be the first major update of the suite, and is
strictly incompatible with previous releases: new benchmarks have been
added, old benchmarks have been removed, all other benchmarks have
been substantially updated. It is for this reason that in any
published use of the suite, the version of the suite must be
explicitly stated.

The release sees the retirement of a number of single-threaded
benchmarks (antlr, bloat and chart), the replacement of hsqldb by
derby, the addition of six completely new benchmarks, and the upgrade
of all other benchmarks to reflect the current release state of the
applications from which the benchmarks were derived. These changes are
consistent with the original goals of the DaCapo project, which
include the desire

Re: [dacapobench-researchers] dacapo bloat benchmark fails on openjdk7

2008-08-27 Thread Steve Blackburn

Luca,

This is not a known problem with DaCapo, so on the face of it, this  
looks like a bug in your version of the VM (perhaps a bug in how you  
built it).


FYI, we maintain 12 hourly performance regressions of a number of VMs  
here:
	http://dacapo.anu.edu.au/regression/perf/2006-10-MR2.html (the latest  
DaCapo release)

and here:
	http://dacapo.anu.edu.au/regression/perf/head.html (the current  
DaCapo svn head).


If there is interest and I can find the time, I may add the OpenJDK  
head to the list of tested benchmarks.


Cheers,

--Steve

On 27/08/2008, at 6:34 PM, Luca Martini wrote:


Apologies for cross posting to the dacapobench-researchers and
[EMAIL PROTECTED] lists.

Hi all,
I recently tried to execute the DaCapo benchmark on OpenJDK 7 and I
found that bloat benchmark fails with the following exception:

$  OpenJDK/jdk7/build/linux-i586/j2re-image/bin/java-jar
~/dacapo-2006-10-MR2.jar bloat
= DaCapo bloat starting =
** Exception while optimizing
transform(LEDU/purdue/cs/bloat/editor/MethodEditor;)Z of class
EDU/purdue/cs/bloat/trans/CompactArrayInitializer
String index out of range: -1802716504
java.lang.StringIndexOutOfBoundsException: String index out of range:
-1802716504
at java.lang.String.getChars(String.java:860)
	at  
java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:408)

at java.lang.StringBuilder.append(StringBuilder.java:136)
at java.lang.StringBuilder.append(StringBuilder.java:132)
at java.util.AbstractCollection.toString(AbstractCollection.java:439)
at
EDU.purdue.cs.bloat.codegen.RegisterAllocator 
$IGNode.toString(RegisterAllocator.java:570)

at java.lang.String.valueOf(String.java:2838)
at java.lang.StringBuffer.append(StringBuffer.java:236)
at EDU.purdue.cs.bloat.util.Graph$4.next(Graph.java:983)
at java.util.AbstractCollection.addAll(AbstractCollection.java:322)
at
EDU 
.purdue 
.cs.bloat.codegen.RegisterAllocator.init(RegisterAllocator.java:288)

at EDU.purdue.cs.bloat.optimize.Main.bloatMethod(Main.java:1078)
at EDU.purdue.cs.bloat.optimize.Main.editClass(Main.java:688)
at EDU.purdue.cs.bloat.optimize.Main.main(Main.java:446)
at dacapo.bloat.BloatHarness.iterate(BloatHarness.java:25)
at dacapo.Benchmark.run(Benchmark.java:126)
at dacapo.TestHarness.runBenchmark(TestHarness.java:302)
at dacapo.TestHarness.main(TestHarness.java:242)
at Harness.main(Harness.java:5)

I really don't know if it's a DaCapo problem or if I missed  
something in
the build process of OpenJDK. The version of the DaCapo is 2006-10- 
MR2.

I built OpenJDK both using mercurial repository and source bundle, and
the build runs fine but when executing the benchmark the same error  
come

up. These are the options I used for building OpenJDK 7:

LANG=C
FINDBUGS_HOME= local path for findbugs
ALT_BOOTDIR=/usr/lib/jvm/java-6-sun
ALT_BINARY_PLUGS_PATH= local path for binary plugs
ANT_HOME=/usr/share/ant
ARCH_DADA_MODEL=32

Here there are some information on my machine:

$ uname -a
Linux 2.6.24-21-generic #1 SMP Tue Aug 12 13:37:22 UTC 2008 i686 GNU/ 
Linux


Any clues? Can anybody confirm such error?
Thanks for your attention,
Luca

--
*
Ing. Luca Martini
Dipartimento di Ing. dell'Informazione
Università di Pisa
Via Diotisalvi, 2, I-56126 Pisa, Italy
Tel: +39 050 2217 465
Fax: +39 050 2217 600
e-mail: [EMAIL PROTECTED]
*

-
This SF.Net email is sponsored by the Moblin Your Move Developer's  
challenge
Build the coolest Linux based applications with Moblin SDK  win  
great prizes
Grand prize is a trip for two to an Open Source event anywhere in  
the world

http://moblin-contest.org/redirect.php?banner_id=100url=/
___
dacapobench-researchers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dacapobench-researchers