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) --

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

Suggest an answer

Log in or Join to answer
Community showcase
Jason Wong
Published 12 hours ago in Agility Beta

Welcome to agility

Every team in the world is unique, and so   Atlassian believes   that each and every team's best way of working  needs to  be molded to their unique circumstances  – ...

231 views 5 14
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot