# Sizing Red Hat Quay: Profiling components to find real limits

DevFeed: [Sizing Red Hat Quay: Profiling components to find real limits](<https://devfeed.tech/articles/sizing-red-hat-quay-profiling-components-to-find-real-limits-106527.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/10/29/sizing-red-hat-quay-profiling-components-find-real-limits>)

Author: Bala Tripura Bodapati

Published: 2026-10-29T13:01:44Z

Content type: article

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [architecture-components](<https://devfeed.tech/topics/architecture-components.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [image manifest](<https://devfeed.tech/topics/image-manifest.md>), [rhel](<https://devfeed.tech/topics/rhel.md>), [Unit testing](<https://devfeed.tech/topics/unit-testing.md>), [The Julia Language](<https://devfeed.tech/topics/julia.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [application](<https://devfeed.tech/tags/application.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [components](<https://devfeed.tech/tags/components.md>), [container](<https://devfeed.tech/tags/container.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [container-image-registry](<https://devfeed.tech/tags/container-image-registry.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [containers](<https://devfeed.tech/tags/containers.md>), [customer](<https://devfeed.tech/tags/customer.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [environments](<https://devfeed.tech/tags/environments.md>), [limits](<https://devfeed.tech/tags/limits.md>), [observability](<https://devfeed.tech/tags/observability.md>), [performance](<https://devfeed.tech/tags/performance.md>), [performance-and-scale-engineering](<https://devfeed.tech/tags/performance-and-scale-engineering.md>), [profiling](<https://devfeed.tech/tags/profiling.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [registry](<https://devfeed.tech/tags/registry.md>), [secure-container-images](<https://devfeed.tech/tags/secure-container-images.md>)

## AI overview

Red Hat Quay has no universal concurrent-pull limit: throughput depends on the whole deployment and must be measured against a documented configuration. In tests using two Quay replicas, NooBaa storage, and 171 MB images, storage endpoints saturated before Quay; increasing them from four to six more than doubled throughput and raised success from 49% to 100%. After storage was scaled, the Python load client became the constraint: its threaded workload hit GIL overhead, and distributing 400 pulls across four client pods improved throughput about 21-fold. At 5,000 concurrent pulls, the test also hit OpenShift's pod PID limit, which the team raised through KubeletConfig and container cgroup settings. The authors recommend profiling each component with observability and treating their results as baselines for that specific setup, not capacity guarantees. Red Hat says it does not currently publish official Quay capacity-planning guidance.

## Source excerpt

Red Hat Quay is a container image registry that stores, distributes, and helps secure container images across on-premise, cloud, and hybrid environments. When a large enterprise customer needed to validate Quay's performance capabilities for their deployment, we turned this sizing request into a systematic method for profiling every component in the architecture. The post Sizing Red Hat Quay: Profiling components to find real limits appeared first on Red Hat Developer.