Performance tuning recommendations
The following are recommended configuration settings for optimal performance of the RapidDeploy web application.
Server recommendations
Depending on the size of your RapidDeploy implementation, the following guidelines are given.
Snapshots vary hugely in size and number taken and so the guidelines here are starting points only.
- Small - Up to 10 projects each consuming 1 new build package per day performing unlimited deployments. User base: 10 users.
- Medium - Up to 30 projects each consuming 1 new build package per day, performing unlimited deployments. User base: 50 users.
- Large - More than 100 projects each consuming 1 new build package per day, performing unlimited deployments. User base: 150+ users
| Framework Server Hardware Minimum Disk Space/RAM | Minimum Disk 5GB, Minimum RAM 2GB |
| Framework Server RapidDeploy Artifact storage | Small: 50GB, Medium: 150GB, Large: 500+ GB |
| Framework Server RapidDeploy Snapshot storage | Small: 50GB, Medium: 150GB, Large: 500+ GB |
| Target server Minimum disk/RAM | Minimum Disk Space in Temporary filesystem (/tmp): 2GB Minimum RAM to perform orchestration jobs: 1Gb |
Server open file descriptors
Please see this document relating to setting file descriptors.
Web container recommendations
| Setting | Description | Suggested Value |
| JVM Heap (Min) | The minimum heap size for the RapidDeply JVM | 512M |
| JVM Heap (Max) | The suggested maximum heap size for the RapidDeply JVM This value is higher than standard settings because concurrent deployments may load large deployment package data of up to 5Mb chunks each. | Small: 768Mb, Medium: 1Gb, Large: 1536Mb (possible clustering needed for larger sites) |
| Web Container thread pool (Max) | The web container may start a number of threads per user, as asynchronous jobs are executed and monitored, and so this value should be set higher than typical default values. | Small: 100, Large: 150+ |
| Session Timeout | Typically users wish to remain signed in for extended periods | 120 Mins |
| Soap conn timeout | RapidDeploy may need to remain connected to target services for extended periods of time. | 600 seconds |
Simultaneous jobs
Please see this document on configuring the maximum number of simultaneous jobs RapidDeploy can run, and thread consideration when setting.