RPM Content Service Performance and Scale Testing
Goals
-
Help pulp_rpm users plan the number of pulp-content apps to serve a given traffic rate for their object-storage backed installation.
-
Determine what the architectural scalability limit is for pulp_rpm content serving.
To achieve these goals in this blog post, I'll be doing two things:
-
Characterize the relationship between sustained requests / sec to the pulp-content app and the number of pulp-content apps without increases in latency.
-
Identify rate limiting components in various test scenarios.