What are the recommended hardware specifications for the Nx Mediaserver application?
The Nx Witness Mediaserver application can be installed on most modern computers with a 64-bit architecture. That being said, Nx Witness, and all software in general, is only as stable as the hardware it is installed upon.
This can range from a low-end affordable CPU with a few GB of RAM on a headless Linux server to demanding systems requiring multiple enterprise-grade Xeon CPUs with powerful Nvidia GPUs, and every configuration in between.
Although the Nx Mediaserver application is an extremely lightweight application that uses a minimum amount of hardware resources, we do recommend using the following hardware specifications for most situations.
| NOTE: These recommendations are derived from extensive stress testing across a wide range of deployment scenarios and incorporate a healthy performance buffer for long-term operational resilience. While these specifications represent our generalized best practices, highly optimized or specialized deployments may require slightly fewer resources. For a truly custom-tailored solution, please engage with your authorized reseller or system integrator. |
Prerequisites
To successfully deploy and operate the Nx Mediaserver application, your host system must meet the following fundamental prerequisites:
- A supported 64-bit Operating System
- An Intel or AMD CPU
| NOTE: The specifications outlined in this document are based on the assumption that the Server is dedicated exclusively to running the Nx Mediaserver application with default settings. Concurrently running resource-intensive third-party applications or services may introduce instability and will likely necessitate a hardware upgrade beyond these recommendations. |
Hardware Recommendations
We recommend using the following specifications and prerequisites mentioned to have good performance for the average Nx Server application:
For Servers with less than 64 connected devices
(HD IP Cameras/IO/Encoders/HD Streams):
| Type | Requirement |
| CPU | Intel i3 or Xeon equivalent with 4 Cores / 8 Threads or more. For specific models please refer to CPUBenchmark for scores of 7,000 or more. |
| RAM | 16GB |
| Network Interface | 2 x 1Gbe (Or more depending on total camera bitrate / Nx Client usage) |
| GPU | Onboard Intel Graphics / Nvidia A400 or equivalent (If basic Nx Client usage is required) |
| OS Drive | Drive Type: SSD or NVME Configuration: Dedicated or Partitioned SSD / NVMe drive Windows: 256GB or higher Ubuntu: 128GB or higher |
| Analytics Drive |
Drive Type: SSD or NVME Please consult the Analytic Usage article for further information for storage sizing. |
| Storage Drive(s) | Responsibility of the storage provider to recommend or validate storage capabilities. |
| Transcoding to Nx Mobile or Web Browser | Max 2ch @ 720p Testing should be conducted by Distributor, SI or End User if transcoding is required. |
For Servers with up to 128 devices
(HD IP Cameras/IO/Encoders/HD Streams):
| Type | Requirement |
| CPU | Intel i3 or Xeon equivalent with 4 Cores / 8 Threads or more. For specific models please refer to CPUBenchmark for scores of 10,000 or more. |
| RAM | 16GB or more |
| Network Interface | 2 x 1Gbe (Or higher depending on total camera bitrate / Nx Client usage) |
| GPU | Onboard Intel Graphics / Nvidia A400 or equivalent (If basic Nx Client usage is required) |
| OS Drive | Drive Type: SSD or NVME Configuration: Dedicated or Partitioned SSD / NVME disk Windows: 256GB or higher Ubuntu: 128GB or higher |
| Analytics Drive |
Drive Type: SSD or NVME Please consult the Analytic Usage article for further information for storage sizing. |
| Storage Drives(s) | Responsibility of the storage provider to recommend or validate storage capabilities. |
| Transcoding to Nx Mobile or Web Browser | Max 2ch @ 720p Testing should be conducted by Distributor, SI or End User if transcoding is required. |
For Servers with up to 256 devices
(HD IP Cameras/IO/Encoders/HD Streams):
| Type | Requirement |
| CPU | Intel i5 or Xeon equivalent with 8 Cores / 16 Threads or more. For specific models please refer to CPUBenchmark for scores of 20,000 or more. |
| RAM | 32GB or more |
| Network Interface | 2 x 1Gbe (Or higher depending on total camera bitrate / Nx Client usage) |
| GPU | Onboard Intel Graphics / Nvidia A400 or equivalent (If basic Nx Client usage is required) |
| OS Drive | Drive Type: SSD or NVME Configuration: Dedicated or Partitioned SSD / NVME disk Windows: 256GB or higher Ubuntu: 128GB or higher |
| Analytics Drive |
Drive Type: SSD or NVME Please consult the Analytic Usage article for further information for storage sizing. |
| Storage Drives(s) | Responsibility of the storage provider to recommend or validate storage capabilities. |
| Transcoding to Nx Mobile or Web Browser | Max 2ch @ 720p Testing should be conducted by Distributor, SI or End User if transcoding is required. |
How did we come to these recommendations?
Our hardware tiers were validated during stress-testing methodologies designed to simulate continuous, operational load. The goal is to ensure long-term system stability without persistent high resource utilization.
A single server stress-test example incorporates the simultaneous execution of the following intensive tasks:
- Recording Load: Ingesting main stream data (e.g., 2.5 Mbps and sub-stream data (e.g., 192 Kbps) while the storage system is actively performing overwrite functions on older footage.
- Remote Live View: Two separate remote Nx Clients simultaneously viewing 8 high-resolution and 8 low-resolution live streams.
- Remote Playback: Two separate remote Nx Clients performing playback, with the timeline manually changed every 60 seconds, viewing 8 high-resolution and 8 low-resolution streams.
- Local Playback: One Nx Client running directly on the server host machine performing playback with the timeline manually changed every 60 seconds.
- Transcoding: Active 720p video transcoding to support mobile or web-browser client access.
- Export Operation: Exporting of a 16-channel, 1-hour video.
Guidance on ARM-Based Devices
Network Optix offers an Nx Mediaserver application designed for ARM-based Linux platforms, including popular single-board computers like the NVIDIA Jetson Nano and Raspberry Pi.
- Production Suitability: Users considering ARM-based devices for production environments must be aware that these deployments require specialized knowledge and experience to ensure long-term stability and reliability.
-
Further Reading:
- Consult the Building Arm-based NVRs support article for detailed guidance on creating a production-ready ARM-based solution.
- Refer to the ARM Support Policy for comprehensive details on platform compatibility and limitations.
In general, if you are looking for low-powered affordable devices, the use of a bare-bone device with 64-bit architecture is recommended as it is easier to set up, more flexible, and more reliable to use in a production environment.
Why We Avoid Stating Minimum Requirements
While the Nx Mediaserver is an extremely efficient application capable of running on low-powered devices, we choose not to publish "minimum" hardware specifications.
The VMS environment involves too many variables, like the number of cameras, recording resolutions, AI applications, rule complexity, client viewing patterns, and concurrent user activity, to define a reliable minimum. For instance, a system with one camera and minimal user interaction would function adequately on very modest hardware, whereas a system managing 2,000 cameras, complex rules, and hundreds of daily user connections necessitates the robust specifications mentioned above.
Comments
0 comments
Article is closed for comments.