Incessant timeouts; slow performance overall

[tmortagne]

@vmassol

@tmortagne I think we forgot to update the doc https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Monitoring It would be nice to document glowroot there.

Done.

[vmassol]

@tmortagne

Done.

Thanks Thomas! I’ve resized it a bit to follow our best practices from https://dev.xwiki.org/xwiki/bin/view/Community/DocGuide#HScreenshots2FImages (was very large)!

[crw]

Two examples:

Performance (XWiki.org)

Performance (XWiki.org)

[vmassol]

@crw

https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Performances/?viewer=changes&rev1=96.1&rev2=97.1

This one is not about the recommended settings. It’s just what we use on xwiki.org.

@crw

https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Performances/?viewer=changes&rev1=53.1&rev2=54.1

Same here.

FTR I had checked before asking you and couldn’t find any recent change of the recommendations which is why I was surprised you mentioned it changed. You said you applied the new settings and I still don’t know what this means. I wanted to make sure I didn’t miss anything.

If you could clarify that would be great.

Thx

[crw]

@vmassol

FTR I had checked before asking you and couldn’t find any recent change of the recommendations which is why I was surprised you mentioned it changed. You said you applied the new settings and I still don’t know what this means. I wanted to make sure I didn’t miss anything.

Let’s go back to the beginning.

1. xwiki was cpu spiking and not returning requests.
2. I changed the CATALINA_OPTS parameters on my server.
3. Things started working.

The old CATALINA_OPTS I was using came from how you run xwiki.org, from years ago. The new CATALINA_OPTS I am now using come from how you are running xwiki.org today.

That’s it.

[vmassol]

Thanks. The xwiki.org settings are actually not recommendations.

So from what you said above at Incessant timeouts; slow performance overall - #17 by crw you just changed the max memory from 512M to 1600M. You also changed the perm size from 196M to 222M. All the other parameters were unchanged)

If you check the recommendations they say:

Small and medium installs: A minimum of 1024MB (-Xmx1024m)
Large installs: 2048MB or beyond (-Xmx2048m).

So you were simply not providing enough memory since the minimum XWiki needs is 1024MB and that’s already part of the recommendations (and FTR this hasn’t changed for about 8-9 years).

So it seems we’re good on the doc side, do you agree?

Thanks and have a great weekend.

[vmassol]

@vmassol

ou also changed the perm size from 196M to 222M. All the other parameters were unchanged)

BTW if you’re on java8, the recommendation also say you don’t need the perm size…

Since XWiki requires java8 since a few years now, you’re probably on java8.

PS: We need to edit the xwiki.org settings since they’re no longer current for the same reason.

[vmassol]

@vmassol

(and FTR this hasn’t changed for about 8-9 years

This is actually not correct. I’ve just noticed that the old recommendation for XWiki < 8.1 for small install was 512MB. I guess we increased the memory need after 8.1.

@vmassol

PS: We need to edit the xwiki.org settings since they’re no longer current for the same reason.

Done.

[pdwalker]

Just gave glowroot a try - it’s even easier to install than javamelody. Thanks for the tip!