Nexus Repository Architecture Reference Spring Revalidation
This documentation aims to update the public reference regarding the capacity of the Nexus Repository after migrating to Spring in release 3.78.0 and some other fundamental changes were introduced. In order to avoid trusting in any outlier, all architecture level results presented are based on statistical average instead of specific test results.
While this is not a complete test for all levels nor formats, it includes a high level validation for the Architecture levels: Architecture 2 (single node with postgres), Architecture 3 (multi-node), and Architecture 4 (multi-node). All tests were carried out with hybrid simulation so this serves as a general reference.
These values derive from calculating 70% of the maximum numbers of requests reached in each architecture.
Profile | Max reached in test (avg) | Current Max Throughput Recommended | New Max. Suggested to recommend(~70% of max) | Mean Time | Pct 95th |
|---|---|---|---|---|---|
Architecture 2 | 268 rps | 100,000 reqs per hour (~28 rps) | 650,000 reqs per hour(~180 rps) | 117 | 122 |
Architecture 3* | 845 rps | 1,000,000 max reqs per hour (~278 rps) | 2,200,000 reqs per hour(~600 rps) | 358 | 392 |
Architecture 4* | 1,754 rps | 2,000,000 max reqs per hour (~555 rps) | 4,800,000 reqs per hour(~1,300 rps) | 289 | 393 |
* These tests required adjustments on the RDS S3 blob store max connection pools (not tested with defaults).