Re: artifactory 2.0.6 speed problems after upgrade

Hi Yoav, sorry about the delay, some more urgent issues arose.

Yoav Landman wrote:

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>

The JVM used is …

# java -version
java version "1.5.0_16"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02)
Java HotSpot(TM) Server VM (build 1.5.0_16-b02, mixed mode)


the output from jmap I obtained by searching for the process ID (grepping ps for artifactory') because I couldn't locate an artifactory-pid file anywhere...

# jmap -heap  24557
Attaching to process ID 24557, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 1.5.0_16-b02

using thread-local object allocation.
Parallel GC with 4 thread(s)

Heap Configuration:
   MinHeapFreeRatio = 40
   MaxHeapFreeRatio = 70
   MaxHeapSize      = 1065353216 (1016.0MB)
   NewSize          = 655360 (0.625MB)
   MaxNewSize       = 4294901760 (4095.9375MB)
   OldSize          = 1441792 (1.375MB)
   NewRatio         = 8
   SurvivorRatio    = 8
   PermSize         = 16777216 (16.0MB)
   MaxPermSize      = 67108864 (64.0MB)

Heap Usage:
PS Young Generation
Eden Space:
   capacity = 21823488 (20.8125MB)
   used     = 388640 (0.370635986328125MB)
   free     = 21434848 (20.441864013671875MB)
   1.780833567942943% used
From Space:
   capacity = 10158080 (9.6875MB)
   used     = 931328 (0.88818359375MB)
   free     = 9226752 (8.79931640625MB)
   9.168346774193548% used
To Space:
   capacity = 10616832 (10.125MB)
   used     = 0 (0.0MB)
   free     = 10616832 (10.125MB)
   0.0% used
PS Old Generation
   capacity = 270794752 (258.25MB)
   used     = 164454496 (156.83602905273438MB)
   free     = 106340256 (101.41397094726562MB)
   60.73031134665416% used
PS Perm Generation
   capacity = 45744128 (43.625MB)
   used     = 45345680 (43.24501037597656MB)
   free     = 398448 (0.3799896240234375MB)
   99.12896361255372% used

I have noticed another thing.  The garbage collection routine seems to be triggering on an hourly basis and taking about 30 minutes to run...

2009-07-07 15:46:14,907 [INFO ] (o.a.j.j.ArtifactoryGarbageCollector:332) - Artifactory Jackrabbit's datastore garbage collector report:
Total execution: 1768280ms :
Data Store Query: 1118620ms
Binary Properties Query: 9680ms
Total Scanning: 1768280ms
Element count: 19067
Total size: 41719982031 bytes

Our monitoring systems are showing a very consistent 'tick' of failures (timeout getting to the login page) on an hourly basis.  Could this garbage collection have anything to do with these issues?

Thanks
Damon