Fisheye/Crucible performance for instance with 150 perforce repositories.

Question

We have a large instance with about 150 perforce repositories with corresponding number of Crucible projects and lots of groups to manage permissions on all these projects and repos.

Right now performance is terrible.

We think that reducing number of repositories, projects and groups will improve performance significantly.

What do you think about this?

Can you suggest reasons for this to work/fail?

We're going to test is in next week or two and I'll bring our results here.

EddieW · Answer

Would be nice if Atlassian provided some of the same suggestions they do for confluence in terms of the GC settings, heap ratios, etc.  It made a huge difference in our Confluence performance.   The fisheye tuning page content on JVM heam is sparce, and basically equates to "more memory!"

EddieW · Answer

ONe peice of advice is to set initial and max memory to the same number. Prevents expensive memory mapping as the heap grows.  MaxNewSize is not the same as Max size,. See this great overview of the heap spaces - http://sureshsvn.com/jvm.html

Andrew Morin · Answer

I am running 2.7.15 as a windows service so my memory settings are in the wrapper.conf file. I have a the following settings...

# Additional Parameters for memory
wrapper.java.additional.11=-XX:MaxPermSize=256m
wrapper.java.additional.12=-Xrs

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=256

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=1024

Is the maxmemory setting the same as MaxNewSize? Our performance is horrible with way less overhead then mentioned in this thread.