Hardware Sizing Matrix
Artifactory system requirements depend mainly upon the expected number of active clients. Use this page to understand sizing, steps, and reference links.
Artifactory Hardware Sizing
Artifactory sizing depends mainly upon the number of active clients.
Use the following matrix to select a baseline profile, then adjust for your repository size, package types, and concurrency pattern.
| Number of Active Clients | Processor (CPU) | Memory |
|---|---|---|
| 0–20 | 4 core | 6 GB |
| 21–100 | 6 core | 12 GB |
| 101–200 | 8 core | 18 GB |
| 201+ | Contact JFrog Support | Contact JFrog Support |
Xray Hardware Sizing
Xray's sizing requirements are determined by the scale of your environment.
Use indexed artifact count as the primary decision input.
Indexed Artifacts | Xray Nodes | CPU (per node) | Memory (per node) | Xray Disk | Database | RabbitMQ |
|---|---|---|---|---|---|---|
Up to 100,000 | 1 | 6 | 24 GB | 500 GB SSD | 500 GB SSD | 1 node: 4 CPU, 8 GB, 100 GB SSD |
Up to 1,000,000 | 2 | 4 | 8 GB | 300 GB per node | 8 CPU, 32 GB, 500 GB SSD | 3 nodes (split): 4 CPU, 8 GB, 100 GB SSD each |
Up to 2,000,000 | 3 | 6 | 12 GB | 300 GB per node | 16 CPU, 32 GB, 1 TB SSD | 3 nodes (split): 4 CPU, 8 GB, 100 GB SSD each |
Up to 10,000,000 | 3 | 8 | 24 GB | 300 GB per node | 16 CPU, 64 GB, 2.5 TB SSD | 3 nodes (split): 4 CPU, 8 GB, 100 GB SSD each |
Over 10,000,000 |
Non-Kubernetes Deployment
Use this section for VM or bare-metal deployments.
Up to 100K indexed artifacts – No High Availability
Component | Nodes | CPU Cores | Memory | Disk Space |
|---|---|---|---|---|
Xray and DB | 1 | 6 | 24 GB | 500 GB SSD |
RabbitMQ | 1 | 4 | 8 GB | 100 GB SSD |
JFrog Advanced Security | 1 | 6 | 24 GB | 500 GB SSD |
Up to 1M indexed artifacts
Component | Nodes | CPU Cores | Memory | Disk Space |
|---|---|---|---|---|
Xray | 2 | 4 | 8 GB | 300 GB |
DB | 1 | 8 | 32 GB | 500 GB SSD |
RabbitMQ (Split) | 3 | 4 | 8 GB | 100 GB SSD |
JFrog Advanced Security | 2 | 8 | 24 GB | 300 GB |
Up to 2M indexed artifacts
Component | Nodes | CPU Cores | Memory | Disk Space |
|---|---|---|---|---|
Xray | 3 | 6 | 12 GB | 300 GB |
DB | 1 | 16 | 32 GB | 1 TB SSD |
RabbitMQ (Split) | 3 | 4 | 8 GB | 100 GB SSD |
JFrog Advanced Security | 4 | 8 | 24 GB | 300 GB |
Up to 10M indexed artifacts
Component | Nodes | CPU Cores | Memory | Disk Space |
|---|---|---|---|---|
Xray | 3 | 8 | 24 GB | 300 GB |
DB | 1 | 16 | 64 GB | 2.5 TB SSD |
RabbitMQ (Split) | 3 | 4 | 8 GB | 100 GB SSD |
JFrog Advanced Security | 8 | 8 | 24 GB | 300 GB |
Over 10M indexed artifacts: Contact JFrog Support
RabbitMQ Note
RabbitMQ is essential for Xray and acts as a message broker between application services.
See: Xray and RabbitMQ Nodes Recommendations
For Xray HA (more than one node or more than 100K indexed artifacts), RabbitMQ and Xray should run on separate servers (split mode).
See: RabbitMQ Split for Xray
Kubernetes Deployment
YAML configuration files for sizing Artifactory, Xray, and Distribution are available on our GitHub.
RabbitMQ Quorum Queues Support (Helm Chart ≥ 103.124)
- JFrog Xray supports RabbitMQ Quorum Queues starting from Helm chart version 103.124.
- Quorum Queues require at least three RabbitMQ nodes for one-node fault tolerance.
- Single-node (non-HA) RabbitMQ remains supported.
- Recommendation: Use a three-node RabbitMQ cluster for Xray. Larger clusters may lower throughput due to replication overhead. JFrog apps are tuned for three-node configurations.
Distribution Hardware Sizing
Minimum requirements when running Distribution with an external database.
Actual requirements may vary with your data size.
| Processor | Memory | Disk Space |
|---|---|---|
| 4 cores | 8 GB | 200 GB SSD |
Updated 2 days ago