Hi,

I completely agree on increasing values on documentation. Obviously 96MB is
not sufficient anymore, even 128M, for sure. Minimum 128MB and recommended
192MB seem ok.

In the meantime, pushing a bit more on investigations is also a good idea,
even if I found your measurements a bit high. From the thread dumps I've
done, I don't remember seeing so mush used memory, even for Home page...

Good luck with that! :-)

Guillaume Fenollar

2013/2/25 Vincent Massol <[email protected]>

> Hi,
>
> I'm going to increase the permgen to 192MB for now since we need XWiki to
> work and I've raised
> http://jira.xwiki.org/browse/XWIKI-8853
>
> Thanks
> -Vincent
>
> On Feb 25, 2013, at 3:01 PM, Vincent Massol <[email protected]> wrote:
>
> > Hi devs,
> >
> > Right now we recommend this on
> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation#HPrerequisites:
> > "A minimum of 300MB of heap memory and 96MB of permGen. Recommended
> values are above 512MB for the heap and 128MB for the permGen (-Xmx512m
> -XX:MaxPermSize=128m)"
> >
> > I've discovered on
> http://ci.xwiki.org/job/xwiki-enterprise-test-extension/org.xwiki.enterprise$xwiki-enterprise-test-extension/1543/consolethat
>  we had an OOM and it seems to happen more and in more in our
> functional tests on CI. Something we've done must have increased our
> permgen memory.
> >
> > I've done some measurements with yourkit and here's what I found:
> > * After XWiki is started and before any page is called we already use
> 64MB of permgen
> > * After calling the home page, the permgen used goes to 101MB
> > * After calling a page using the code macro, the permgen goes to 132MB
> >
> > So it seems that your default value of 96MB and recommended value of
> 128MB are not enough…
> >
> > BTW forcing garbage collection reduces from 132MB to 130MB (not much).
> >
> > We need to either find what is taking all our permgen memory or if it's
> legit increase our recommendations and the default value we use in
> start_xwiki.sh/bat
> >
> > Any idea?
> >
> > My hunch tells me the Extension Manager could be the cause.
> >
> > Thanks
> > -Vincent
>
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs
>
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to