Hardware Requirements
The hardware requirements vary depending on multiple factors including: the deployment type (combo, cluster, or high availability), seat count, repository size, and usage patterns. This page provides guidelines that help estimate the required hardware specifications.
Helix TeamHub is written to be efficient and lightweight. However, due to the nature of the product, most of the activities trigger calls to the underlying version control system. Keeping this in mind makes choosing the right hardware easier because TeamHub usage is estimated along with the underlying components.
Minimal Requirements
The Helix TeamHub technology stack consists of a number of components. For them to stay coherent, the following minimum hardware specifications are required for any server with a TeamHub installation:
Resource | Requirement |
---|---|
CPU | 2.6GHz |
Memory | 4GB |
Root disk | 40GB |
Data Storage | High-performance SAN or locally attached storage |
Determining hardware capacity requirements
TeamHub is battle-tested to serve thousands of users. The variation in usage patterns makes it hard to give accurate numbers, but the following matrix can be used as reference based on past experience.
Seats | Memory | CPU Cores | Root Disk Space |
---|---|---|---|
0-100 | 8GB | 2 | 40GB |
100-500 | 16GB | 4 | 40GB |
500-1000 | 32GB | 8 | 40GB |
1000-2000 | 64GB+ | 16 | 40GB |
Because the system deals with a lot of IO operations to the repositories on disk, it is recommended to have an ultra-fast (SSD/SAN) data storage with speedy access.
Further assistance
For questions or concerns about performance issues and/or capacity management, don't hesitate to contact the Helix TeamHub Support Team.