---
title: "Minimum System Requirements for NIOS-X Servers"
canonical: "https://docs.infoblox.com/space/BloxOneInfrastructure/873758806/Minimum%20System%20Requirements%20for%20NIOS-X%20Servers"
format: markdown
---
> ❌ **Important Note**
> ❌
> ❌ The minimum system requirements listed below must be dedicated to the NIOS-X server you plan to deploy. These resources must not be shared with or used by other non-Infoblox applications. Doing so will negatively affect the performance of your Infoblox Platform services. For information about port usage and other requirements, see the following:
> ❌
> ❌ - *[Firewall Requirements for Infoblox Cloud Services](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/873660456)*
> ❌ - *[Supported Platforms for NIOS-X Servers](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/873693279)*
> ❌ - *[Port Usage for Bare-Metal NIOS-X Servers](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/873758860)*
# Virtual Deployments
**About Sizes:** Form factors (2XS, XS, S, M, L, etc.) apply to NIOS‑X servers that run DNS or DHCP services and reflect entitlement to certain guardrails of DNS QPS, DHCP LPS, and server-based object count. NIOS‑X servers that do not run DNS or DHCP services do not utilize server tokens. For Discovery guidance, see *[Minimum system requirements for NIOS-X Discovery](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/1361543714)*.
The following table describes the supported NIOS-X virtual server form factors, their specifications, and token allocation.
> 📝 Token usage is determined by actual usage, not by server specification. For example, you can deploy a NIOS-X server with 8 vCPU and 8 GB RAM and configure it as an XS form factor (using 250 tokens). If server usage increases and exceeds the limit of an XS server (e.g., QPS goes from 9k to 12k), the token consumption of that server will automatically change from XS (250 tokens) to S (470 tokens) without the need to add more CPU/RAM.
For information on NIOS-X licensed form factors and token requirements, please see *[Universal DDI Licensing](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneDDI/pages/846954761)*.
| **Performance ** | **Specifications** |
| --- | --- |
| **kQPS** | **LPS** | **CPU** | **RAM** | **Storage** |
| 5 | 75 | 3 Core | 4 GB | 64 GB |
| 10 | 150 | 3 Core | 4 GB | 64 GB |
| 20 | 200 | 4 Core | 4 GB | 128 GB |
| 40 | 300 | 4 Core | 32 GB | 1 TB |
| 70 | 400 | 16 Core | 32 GB | 1 TB |
| 115 | 675 | 24 Core | 32 GB | 1 TB |
> ℹ️ The minimum system requirements for virtual deployments are applicable for running a single service on the host. If multiple services are deployed, additional resources may be required.
> ❌ For Data Connector service, you need a virtual appliance with a minimum of 8 vCPUs, 16 GB memory, and 750 GB storage.
# Bare-Metal Deployments
The following table lists the recommended minimum system requirements for bare-metal deployments:
| | **Small Branches** | **Medium Branches** | **Large Branches** |
| --- | --- | --- | --- |
| **CPU** | 8-core Intel Atom
@2 GHZ | 8-core Intel Atom
@2.2 GHZ | 8-core Intel Xeon
@2 GHZ |
| **DRAM** | 16 GB | 16 GB | 32 GB |
| **Storage** | 64 GB | 120 GB | 1 TB |
| **Ports** | 2 x 1G | 2 x 1G; 2 x 10G | 2 x 1G; 2 x 10G |
> ⚠️ **Note**
> ⚠️
> ⚠️ If your system does not meet the recommended minimum system requirements, you might encounter compatibility issues with Infoblox Platform's expected performance. Infoblox is not liable for any issues as a result of non-conformance with the required specifications. Infoblox also does not guarantee performance based on your system configuration. Procurement and maintenance of the system are your responsibilities. To the extent that Infoblox processes Personal Data on your behalf for provision of services, the terms and conditions in the *[Data Processing Addendum (“DPA”)](https://www.infoblox.com/company/legal/data-processing-addendum/)* shall apply. Personal Data is defined in the DPA.
# NIOS-X Server Performance Reference
Infoblox Platform offers flexible scalability to meet your changing business needs from the smallest to the largest locations. To simplify planning, site tiers are suggested below, followed by reference specifications to approximate these performance targets.
In the table below, cache hit ratio (CHR) measures how many requests a cache can deliver successfully from its cache storage, compared to how many requests it receives.
> ❌ **Important Note**
> ❌
> ❌ The stated numbers and recommendations in the following table are for reference only. They represent the results of lab testing in a controlled environment. Enabling additional protocols, services, cache hit ratio for recursive DNS, and customer environment variables will affect performance. To design and size a solution for a production environment, please contact your Infoblox Solution Architect.
| **Recommended for** | **Small Branches** | **Medium Branches** | **Large Branches** |
| --- | --- | --- | --- |
| **DNS Queries Per Second (QPS)** | 160 @ 0% CHR, 681 @ 85% CHR, 1.6K @ 100% | 700 @ 0% CHR, 2.9K @ 85% CHR, 7K @ 100% CHR | 3.5K @ 0% CHR, 14.8K @ 85% CHR, 35K @ 100% CHR |
| **DHCP Leases Per Second (LPS)** | 25 | 300 | 400 |
| **Hardware** | Infoblox B1-105.
For more information, see *[Infoblox B1-105 Appliance](https://docs.infoblox.com/space/BloxOneDDI/186369222/BloxOne+B1-105+Appliance)*. | Dell VEP-1425 (Infoblox B1-212). For more information, see *[Infoblox B1-212 Appliance](https://docs.infoblox.com/space/BloxOneDDI/413960530/BloxOne+B1-212+Appliance)*. | Dell VEP-1485 |