Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,363,844
Community Members
 
Community Events
168
Community Groups

Best Practices for high load instances

We need 100+ projects and 1000+ users hosted on single Crucible instance.

Do you know any performance limitations, or best practices for hardware/instance configurations we may run Crucible without performance issues?

1 answer

This is probably a little late, but I noticed there was no answer...

We currently run Crucible with 300+ projects and around 800 users and we only have problems if people have particularly large code reviews (usually a result of bad practices or waterfall development) or if there are anomolies in the Subversion commit.

I'm not sure what the limit is for a Crucible instance but in my experience it seems more limited by project size than amount of projects.

I find it works best with multi-threading enabled (we use 3 threads for initial scans and incremental) and also increase your Java heap to a reasonable size for your instance. We use max 2GB. This information is in the docs on performance tuning I think.

There's a problem with InfinityDB cache (its size is not capped and may exhaust heap of any size) -- https://jira.atlassian.com/browse/FE-4427

There's a workaround, but it causes a 10-15% performance hit

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events