We're running Crucible/Fisheye 4.1.1 on an 8GB Windows server, as a Windows service. The process does not appear to be CPU- or memory-bound. It is currently using about 4.5GB of a 6GB allocated heap. CPU usage looks fine. However, response times for certain operations is REALLY slow. For example, an individual user's home page renders quickly, but it takes 6-7 seconds for the Recent Activity and Projects areas to populate. I've tried this with a browser installed on the same server where Crucible runs, and it made no difference. Another example of particular slowness is adding a reviewer to a review. It can take 4-5 seconds to pull up the list of reviewers.
We've got about 160 repositories, 120 projects, and 500 users.
What steps can we take to diagnose or fix this issue?
There are plenty of factors that might affect Crucible performance. As CPU and memory is ruled out, the first thing that comes to my mind is IO – DB or file system, especially if one of them is not accessed locally.
We usually start with looking at the application logs and most of the times that enables us to pinpoint the problem.
Could you please report your issue on support.atlassian.com? To save some time you could turn DEBUG logs on (Administration > Global Settings > Server > Debug Logging), load a bunch of slowly responding pages, generate a Support ZIP (Administration > System Settings > Support Tools > Create Support Zip) and attach it to your ticket. Thanks!
FishEye & Crucible Team
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
An efficient enterprise content management system, or ECM, is a must-have for companies that create work online (cough cough, all companies). If content calendars, marketing plans, and bu...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs