Re: [rvm-research] issues with dacapo benchmarks

Johannes Sinsel <[email protected]> Mon, 25 Mar 2019 16:21:41 +0100
Newsgroups gmane.comp.java.jikes.rvm.devel
Message-ID <[email protected]> 
This is a multi-part message in MIME format.
--===============7447529054384754772==
Content-Type: multipart/alternative;
 boundary="------------47E0430FE0A8C118A6A69E7C"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------47E0430FE0A8C118A6A69E7C
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hey,

with changes to the heap size, everything works perfectly fine, thanks :)

Kind regards,
Johannes

On 21.03.19 18:55, Erik Brangs wrote:
> Hi,
>
> On 21.03.19 10:21, Johannes Sinsel wrote:
>> the Jikes User Guide recommends the Dacapo benchmark from 2006 for 
>> testing.
>> With the current version of Jikes, there is a problem with (I think 
>> more memory intensive) benchmarks, like eclipse and hsqldb, also 
>> chart is not working, but this seems to be due to AWT-support and 
>> appeared in earlier versions, too.
>> After several GC Warnings, the VM chrashes in eclipse. There are also 
>> GC Warnings in hsqldb, but I stopped the execution after like five 
>> minutes.
>
> You will need to set the heap size for the benchmarks if you're 
> running them manually. The dacapo test set has predefined heap sizes. 
> You can find those in testing/tests/dacapo/build.xml .
>
> There are more test sets in testing/tests but not all of them are 
> readily usable. The following ones should mostly work:
> - basic and opttests should always pass on x86/x64 (TestSysCalls fails 
> on PowerPC)
> - jni should always pass on x86/x64 (TestNestedGC fails on PowerPC)
> - gctest should mostly pass (Exhaust fails sometimes, ReferenceTest 
> fails sometimes on a few collectors, InlineAllocations fails when only 
> using opt compiler)
>
>> I used the prototype-opt build.
>
> I've attached an example test run file with protoype-opt and dacapo. 
> You can put it into build/test-runs and then use it with Ant or 
> buildit. Depending on how much functional testing you want to do, it 
> may be profitable to use "development" instead of "protoype-opt".
>
>
> Kind regards,
>
> Erik Brangs
>
>
>
>
> _______________________________________________
> Jikesrvm-researchers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers

--------------47E0430FE0A8C118A6A69E7C
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hey,</p>
    <p>with changes to the heap size, everything works perfectly fine,
      thanks :)</p>
    <p>Kind regards,<br>
      Johannes<br>
    </p>
    <div class="moz-cite-prefix">On 21.03.19 18:55, Erik Brangs wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:[email protected]">Hi,
      <br>
      <br>
      On 21.03.19 10:21, Johannes Sinsel wrote:
      <br>
      <blockquote type="cite">the Jikes User Guide recommends the Dacapo
        benchmark from 2006 for testing.
        <br>
        With the current version of Jikes, there is a problem with (I
        think more memory intensive) benchmarks, like eclipse and
        hsqldb, also chart is not working, but this seems to be due to
        AWT-support and appeared in earlier versions, too.
        <br>
        After several GC Warnings, the VM chrashes in eclipse. There are
        also GC Warnings in hsqldb, but I stopped the execution after
        like five minutes.
        <br>
      </blockquote>
      <br>
      You will need to set the heap size for the benchmarks if you're
      running them manually. The dacapo test set has predefined heap
      sizes. You can find those in testing/tests/dacapo/build.xml .
      <br>
      <br>
      There are more test sets in testing/tests but not all of them are
      readily usable. The following ones should mostly work:
      <br>
      - basic and opttests should always pass on x86/x64 (TestSysCalls
      fails on PowerPC)
      <br>
      - jni should always pass on x86/x64 (TestNestedGC fails on
      PowerPC)
      <br>
      - gctest should mostly pass (Exhaust fails sometimes,
      ReferenceTest fails sometimes on a few collectors,
      InlineAllocations fails when only using opt compiler)
      <br>
      <br>
      <blockquote type="cite">I used the prototype-opt build.
        <br>
      </blockquote>
      <br>
      I've attached an example test run file with protoype-opt and
      dacapo. You can put it into build/test-runs and then use it with
      Ant or buildit. Depending on how much functional testing you want
      to do, it may be profitable to use "development" instead of
      "protoype-opt".
      <br>
      <br>
      <br>
      Kind regards,
      <br>
      <br>
      Erik Brangs
      <br>
      <br>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
Jikesrvm-researchers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers">https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers</a>
</pre>
    </blockquote>
  </body>
</html>

--------------47E0430FE0A8C118A6A69E7C--


--===============7447529054384754772==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============7447529054384754772==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Jikesrvm-researchers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers

--===============7447529054384754772==--