archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sascha Vogt <>
Subject Re: Performance issues after upgrading to 2.0.1
Date Thu, 17 Apr 2014 09:14:35 GMT
Hi Olivier,

Am 17.04.2014 01:24, schrieb Olivier Lamy:
> DefaultISMLocking is a jackrabbit class
> Maybe try change the log4j2 async configuration?
> See
> Due to various issues reported here, I will change the default.

We've already changed that, didn't change anything (we have no CPU issue
here). Also in the meantime I added 4 more cores (so currently 8) -
average load is at 2, so plenty of free CPU cycles for Archiva.

Do you have any idea about the other things? Or a starting point where
we should debug / profile?

View raw message