« Return to Thread: artifactory 2.0.6 speed problems after upgrade

Re: artifactory 2.0.6 speed problems after upgrade

by Yoav Landman :: Rate this Message:

Reply to Author | View in Thread

Hi Damon,

Can you post the output of running the following once you experience slowdowns + specify the exact JVM version you are using:

jmap -heap <artifactory-pid>

Thanks,

Yoav

On Tue, Jun 30, 2009 at 2:25 PM, damonjebb <djebb@...> wrote:


freddy33 wrote:
>
> A lot of things changed in 2.0 :), but to make sure:
> - Which OS are you using?
>

Redhat EL 4.


freddy33 wrote:
>
> - Do you use a Web container or the standalone Jetty?
>

I'm running a tomcat container behind a httpd (apache).  Our previous
configuration used a 'worker' configuration pointed at the ajp connector on
tomcat.  The httpd is on a separate server from the artifactory one.


freddy33 wrote:
>
> - Do you use Derby DB or an external DB?
>

Using the derby database


freddy33 wrote:
>
> - Is the artifactory home (especially the data folder) on a remote disk or
> local?
>

Local disk


freddy33 wrote:
>
> - How much JVM heap size did you configured (default is 1Gb when
> installing
> the Unix service: /etc/artifactory/default )
>

I haven't configured any special options for the JVM that's running the
tomcat - which is exactly the same as was working ok with the previous
version.  I'm not seeing any log messages that indicate a problem with the
memory available to artifactory (or anything else)

I wanted to make the minimum changes before looking at any optimisations for
the new version, which is why the configuratin, jvm setup, etc. have not
changed yet.

Since posting I have tried to use the instructions in the artifactory manual
for running behind a httpd using proxying, but they do not work for me (I
get 'permission denied' errors for all pages).

I can connect directly to the artifactory server on the http port configured
for the tomcat container - this works in much the same way as the one behind
apache on the other server and has been seen to 'hang' too.

I've looked more closely at the memory usage and do not think that there is
a significant problem with memory - I had assumed that exceeding physical
memory and using the swap space was the most likely cause of wait-states,
but there is little evidence for this now.  Free looks like this...

# free -m
            total       used       free     shared    buffers     cached
Mem:          4057       4031         25          0          8       3416
-/+ buffers/cache:        607       3449
Swap:         2047          0       2047

seems like 3/4 of the memory is currently available and we still get slow
downs and high percentages of waits.

Any suggestions for things that I could look at to see what could be
bottlenecking the system would be gratefully received!

Thanks.
Damon

--
View this message in context: http://www.nabble.com/artifactory-2.0.6-speed-problems-after-upgrade-tp24269554p24270973.html
Sent from the Artifactory-Users mailing list archive at Nabble.com.


------------------------------------------------------------------------------
_______________________________________________
Artifactory-users mailing list
Artifactory-users@...
https://lists.sourceforge.net/lists/listinfo/artifactory-users


------------------------------------------------------------------------------

_______________________________________________
Artifactory-users mailing list
Artifactory-users@...
https://lists.sourceforge.net/lists/listinfo/artifactory-users

 « Return to Thread: artifactory 2.0.6 speed problems after upgrade