<div dir="ltr"><div><div>The problem is that we still leak threads in almost every module, and that means we keep a copy of the core classes (and all their dependencies) for every module. Of course, some modules' dependencies are already oversized, so keeping only one copy is already too much...<br>
<br></div>I admit I don't run the whole test suite too often either, but I recently changed the Cloudbees settings to get rid of the OOM there. It uses about 550MB of permgen by the end of the test suite, without -XX:+UseCompressedOops. These are the settings I used:<br>
<br>-server -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+UseParNewGC -XX:+CMSClassUnloadingEnabled -XX:NewRatio=4 -Xss500k -Xms100m -Xmx900m -XX:MaxPermSize=700M<br><br></div><div></div><div><br></div><div>Cheers<br>
</div><div>Dan<br><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 20, 2013 at 2:59 PM, Tristan Tarrant <span dir="ltr"><<a href="mailto:ttarrant@redhat.com" target="_blank">ttarrant@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Sanne, turn on CompressedOops ? Still those requirements are indeed<br>
ridiculous.<br>
<span class="HOEnZb"><font color="#888888"><br>
Tristan<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On 03/20/2013 01:27 PM, Sanne Grinovero wrote:<br>
> I'm testing master, at da5c3f0<br>
><br>
> Just killed a run which was using<br>
><br>
> java version "1.7.0_17"<br>
> Java(TM) SE Runtime Environment (build 1.7.0_17-b02)<br>
> Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)<br>
><br>
> this time again an OOM (while I have 2GB !), last sign of life came<br>
> from the "Rolling Upgrade Tooling"<br>
><br>
> I'm not going to merge/review any pull request until this works.<br>
><br>
> Sanne<br>
><br>
> On 20 March 2013 12:09, Mircea Markus <<a href="mailto:mmarkus@redhat.com">mmarkus@redhat.com</a>> wrote:<br>
>> I've just run it on master and didn't get OOM. well I'm using osx. Are you running it on master or a particular branch? Which module crashes?<br>
>> e.g. pedro's ISPN-2808 adds quite some threads to the party - that's the reason it hasn't been integrated yet.<br>
>><br>
>> On 20 Mar 2013, at 11:40, Sanne Grinovero wrote:<br>
>><br>
>>> Hi all,<br>
>>> after reviewing some pull requests, I'm since a couple of days unable<br>
>>> to run the testsuite; since Anna's fixes affect many modules I'm<br>
>>> trying to run the testsuite of the whole project, as we should always<br>
>>> do but I admit I haven't done it in a while because of the core module<br>
>>> failures.<br>
>>><br>
>>> So I run:<br>
>>> $ mvn -fn clean install<br>
>>><br>
>>> using -fn to have it continue after the core failures.<br>
>>><br>
>>> First attempt gave me an OOM, was running with 1G heap.. I'm pretty<br>
>>> sure this was good enough some months back.<br>
>>><br>
>>> Second attempt slowed down like crazy, and I found a warning about<br>
>>> having filled the code cache size, so doubled it to 200M.<br>
>>><br>
>>> Third attempt: OutOfMemoryError: PermGen space! But I'm running with<br>
>>> -XX:MaxPermSize=380M which should be plenty?<br>
>>><br>
>>> This is :<br>
>>> java version "1.6.0_43"<br>
>>> Java(TM) SE Runtime Environment (build 1.6.0_43-b01)<br>
>>> Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)<br>
>>><br>
>>> MAVEN_OPTS=-Xmx2G -XX:MaxPermSize=380M -XX:+TieredCompilation<br>
>>> -Djava.net.preferIPv4Stack=true -Djgroups.bind_addr=127.0.0.1<br>
>>> -XX:ReservedCodeCacheSize=200M<br>
>>> -Dlog4j.configuration=file:/opt/infinispan-log4j.xml<br>
>>><br>
>>> My custom log configuration just disables trace & debug.<br>
>>><br>
>>> Going to try now with larger PermGen and different JVMs but it looks<br>
>>> quite bad.. any other suggestion?<br>
>>> (I do have the security limits setup properly)<br>
>>><br>
>>> Sanne<br>
>>> _______________________________________________<br>
>>> infinispan-dev mailing list<br>
>>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
>> Cheers,<br>
>> --<br>
>> Mircea Markus<br>
>> Infinispan lead (<a href="http://www.infinispan.org" target="_blank">www.infinispan.org</a>)<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> infinispan-dev mailing list<br>
>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
><br>
<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</div></div></blockquote></div><br></div>