We are migrating a 2000-plus user Atlassian Stash v3.7.1 instance currently running on RHEL5 hosts to newer RHEL7 hosts. After migrating, we will update to a more-current version of bitbucket.
The current system runs on a very large set of shared Linux systems. We are considering moving to right-sized VMs and need guidance on sizing the new hosts -- particularly memory and CPU.
We are looking for help in making that sizing determination.
Regards
Hi James,
For guidance on the right size, I'd recommend you to visit the article Scaling Bitbucket Server. Keep in mind that sizing is based on the number and size of repositories and number of operations, so the number of users is not really relevant for this.
For the upgrade, you can follow Bitbucket Server upgrade guide. Note that you're jumping a few versions and there's been many changes so make sure to read all the documentation before proceeding. Also, we advise you to do the upgrade first on a testing environment to make sure everything works as expected. One of these changes is that we dropped server.xml, so if you have any configuration changes you should add them to bitbucket.properties. For more information on this part, please read Migrate server.xml customizations to bitbucket.properties.
Another important article is Supported platforms.
And lastly, since you're using Linux, please also read the page Install Bitbucket Server on Linux.
I believe that will provide you with all the information you need for this upgrade. If you have any questions or something is not clear, please let us know and we'll be happy to continue helping you!
Best regards,
Ana
Hi Ana,
Thanks for your answer, but I have to say: I am looking for more of a feel answer. The links you have provided are quite detailed and messy.
I am looking for a back of the envelope indicator that says: roughly speaking here are the categories of sizing and the main factors driving the decision.
So, for example: low, medium and large scale platforms and what are the drivers for each. As well as a discussion of VM versus physical.
Regards,
-James O'Connell
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi James, thanks for clarifying your needs.
We help you obtain your own estimates on the first article I posted, for example:
Memory
When deciding on how much memory to allocate for Bitbucket Server, the most important factor to consider is the amount of memory required for Git. [...] For large repositories, it is not uncommon for Git to use up to 500 MB of memory during the clone process. As a rule of thumb 1.5 x the repository size on disk (contents of the .git/objects directory) is a rough estimate of the required memory for a single clone operation for repositories up to 400 MB. For larger repositories, memory usage flattens out at about 700 MB.
In general, the default memory settings (max. 768 MB) should be sufficient to run Bitbucket Server.
Database requirements
The size of the database required for Bitbucket Server depends in large part on the number of repositories and the number of commits in those repositories.
A very rough guideline is: 100 + ((total number of commits across all repos) / 2500) MB.
If you want something more tailored to your needs, or someone studying your particular case, we don't' provide that kind of services but we have multiple partners that can help you with personalized guidance, recommendations on your specific requirements, and answer all your questions regarding your configuration. You can find the right partner for you here.
Hope that helps you, James. If you need anything else from our side, let us know!
Kind regards,
Ana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.