Azure Sizing

When deploying a self-managed deployment of the JFrog Platform on Azure, it is important to consider the hardware and sizing requirements to ensure optimal performance and scalability.

The following guidelines are recommended for sizing your Azure infrastructure.

Artifactory

NOTES:

Each Artifactory replica should run in its own instance (prefer a dedicated node pool)
Each Nginx replica should run in its own instance (prefer a dedicated node pool)
Distribution can run on the Artifactory nodes

Size Template	Small	Medium	Large	XLarge	2XLarge
Number of Artifactory Replicas	1	2	3	4	6
Number of Nginx Replicas	1	2	2	2	3

Artifactory node pool instance	Standard_D8s_v6	Standard_D8s_v6	Standard_D16s_v6	Standard_D16s_v6	Standard_D16s_v6
CPU	8	8	16	16	16
Memory	32	32	64	64	64

Nginx node pool instance	Standard_F4s_v2	Standard_F4s_v2	Standard_F4s_v2	Standard_F8s_v2	Standard_F8s_v2
CPU	4	4	4	8	8
Memory	8	8	8	16	16

Azure Flexible Server instance	E8ds_v6	E16ds_v6	E20ds_v6	E32ds_v6	E48ds_v6
CPU	8	16	20	32	48
Memory	64	128	160	256	384
Max connections	100	200	600	2000	5000

Xray

NOTES:

Each Xray replica should run in its own instance (prefer a dedicated node pool)
Xray has HPA enabled, so more instances should be available if needed
If running JAS, it’s recommended to use a dedicated node pool for it to protect Xray and Artifactory pods

Size Template	Small	Medium	Large	XLarge	2XLarge
Number of Xray Replicas	1	1	1	2	3

Xray node pool instance	Standard_F8s_v2	Standard_D8s_v6	Standard_D8s_v6	Standard_D8s_v6	Standard_D8s_v6
CPU	8	8	8	8	8
Memory	16	32	32	32	32

JAS node pool instance	Standard_D8s_v6	Standard_D8s_v6	Standard_D8s_v6	Standard_D8s_v6	Standard_D8s_v6
CPU	8	8	8	8	8
Memory	32	32	32	32	32

Azure Flexible Server instance	E4ds_v6	E8ds_v6	E16ds_v6	E20ds_v6	E32ds_v6
CPU	4	8	16	20	32
Memory	16	32	64	160	256
Max connections	200	500	600	1200	2000

Storage

See Storage Specifications for details on storage requirements and recommendations.