archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff <predato...@gmail.com>
Subject Re: Performance when resolving artifacts...
Date Tue, 07 Aug 2012 20:03:21 GMT
Hmm...yes and yes (though getting external artifacts seem slow, even after
they are cached in archiva).

I have one group, with 6 managed repositories:

   - 3rd-party-releases
   - 3rd-party-snapshots
   - team1-releases
   - team1-snapshots
   - team2-releases
   - team2-snapshots


In the 3rd party repos, I am proxying various externals including central,
java.net, etc. and some others.

I'll look into how to exclude our stuff from externals.  I've not done it
before.

Thanks!!

On Tue, Aug 7, 2012 at 1:55 PM, Olivier Lamy <olamy@apache.org> wrote:

> Are you using a repository group with a lot of repositories
> (internals, mavencentral etc...) ?
> Does it happen when you want to download internal snapshots ?
> If yes maybe you must exclude com.yourcompany from external repositories.
>
> 2012/8/7 Jeff <predatorvi@gmail.com>:
> > I haven't yet had the time to dig yet.  Been stretched to thin.  I was
> > hoping someone had an inkling as to where to start looking.  I'm running
> > 1.4-M2 so if the referenced patch is fixed, then I've definitely got
> other
> > issues.
> >
> > On Tue, Aug 7, 2012 at 1:36 PM, Charles Kim <charlesk@yahoo-inc.com>
> wrote:
> >
> >> Have you tried profiling it to see where the bottleneck is?  We have
> also
> >> run into performance issues as well.  Not sure if 1.4-M2 addresses this
> >>
> http://jawspeak.com/2010/11/28/spring-slow-autowiring-by-type-getbeannamesfortype-fix-10x-speed-boost-3600ms-to/butwe
patched it on our build.
> >> Another place we've looked was the authentication where it created a lot
> >> of HTTP sessions as part of the authentication.
> >>
> >> -----Original Message-----
> >> From: Jeff [mailto:predatorvi@gmail.com]
> >> Sent: Tuesday, August 07, 2012 10:32 AM
> >> To: users@archiva.apache.org
> >> Subject: Performance when resolving artifacts...
> >>
> >> I'm running Archiva 1.4-M2.
> >>
> >> When I do a build from any of our dev machines or build server, it
> takes a
> >> long time to pull even just the POM files from Archiva.
> >>
> >> Typical times for POM files are:
> >>
> >> (826 B at 0.7 KB/sec)
> >> (3 KB at 0.2 KB/sec)
> >> (834 B at 0.6 KB/sec)
> >> (822 B at 0.8 KB/sec)
> >>
> >> Is this normal?  I really would have expected much, MUCH faster.  The
> >> server is dedicated to Archiva running on Tomcat so there should not be
> any
> >> resource problems and it is running CentOs 6.2 w/ 4GB RAM, dual core CPU
> >> and tomcat configured to use 3GB of that.
> >>
> >> Could it be searching all repositories in my group, including all
> proxies
> >> regardless of the artifact?
> >>
> >> Is there something to help me tune it better?
> >>
> >>
> >> Thanks!
> >>
> >> --
> >> Jeff Vincent
> >> predatorvi@gmail.com
> >> See my LinkedIn profile at:
> >> http://www.linkedin.com/in/rjeffreyvincent
> >> I ♥ DropBox <http://db.tt/9O6LfBX> !!
> >>
> >
> >
> >
> > --
> > Jeff Vincent
> > predatorvi@gmail.com
> > See my LinkedIn profile at:
> > http://www.linkedin.com/in/rjeffreyvincent
> > I ♥ DropBox <http://db.tt/9O6LfBX> !!
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>



-- 
Jeff Vincent
predatorvi@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
I ♥ DropBox <http://db.tt/9O6LfBX> !!

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message