Maybe one of the remote repositories being proxied went down so the proxying is taking a while? You can switch on the debug logs too in ../WEB-INF/classes/log4j.xml to help better track down the cause.
-Deng On Wed, May 12, 2010 at 12:02 AM, Michael Delaney <[email protected]>wrote: > All, > > Within the past few weeks the performance of my Archiva 1.1.4 installation > has tanked. Where it use to take a couple seconds to download a small jar it > now takes twenty seconds or more for the same jar file or even worse a pom > file. > > I haven't changed the configuration in some time, so the decrease in > performance can't be tracked back to a configuration change. I have site > time outs set, as well as pretty strict white/black lists. I'm pretty > stumped as to where Archiva is spending it's time. > > The system Archiva is running on has about 500Mb free memory as well as > lots of swap and disk space. > > What's the best way to try to debug performance on Archiva? >
