Skip to main content

Sonatype Nexus Repository High Availability Performance Data Using Azure

For full transparency and to help you evaluate whether a High Availability (HA) Sonatype Nexus Repository deployment is right for your organization, we are providing findings from our internal performance testing.

Test Focus and Limitations

All of the results detailed below have been gathered in Azure deployments. We do not have our own datacenter or dedicated hardware hosts aside from our engineers’ personal development environments.

Our focus for the internal stress testing was to validate the stability of our product in a common deployment scenario.

Summary of Findings

  • Achieved 208 requests per second (RPS).

  • At this throughput, we achieved our target success rate, exceeding successful responses for more than 99% of requests.

  • Response time distribution was as follows:

    • 91.8% achieved 75ms

    • 4% achieved 225ms

    • 1% achieved 376ms

  • Sonatype Nexus Repository nodes' CPU loads did not exceed 20%.

  • Database CPU load did not exceed 30%.

  • There was no significant difference in RPS or other measures (e.g., Response time distribution) between standard and premium Azure block storage.

  • You may achieve lower or greater RPS depending on your workload. Formats with larger assets (e.g., Docker) may see lower RPS, while formats with smaller assets (e.g., Maven, NuGet, and npm) may see higher RPS.

Test Environment

  • 3 Sonatype Nexus Repository nodes

    • 8vCPU (each)

    • 32GiB RAM (each)

  • 1 PostgreSQL database node

    • 4vCPU

    • 16GiB RAM

  • Tested both Standard and Premium Block Blob Azure storage options

Discussion

  • At the scale described above, the Azure Virtual Machines and the database are modestly utilized (12-20%).

  • This is a significant deployment scale that most customers do not need to consider.

  • For customers that exceed these throughput thresholds, individualized analysis of available technology is needed.

  • Successful deployments at higher scale or with other technology platforms requires our customers having significant in-house expertise.

Resources Use Sample

The next graphs reflect a sample of the resource use for our tests. This information is a good reference for the general behavior of a system under the tested conditions.

Per-Node CPU Use

185237573.png

RDS CPU Use

186155368.png

Average Throughput

186155369.png

Conclusion

Sonatype Nexus Repository's Azure HA solution achieved a throughput of 208 RPS with successful responses for >99% of requests. However, the anticipated cost for maintaining the significant deployment required to achieve HA is high and therefore not appropriate for most customers.