0% found this document useful (0 votes)
90 views9 pages

SecurOS System Specs v.2.7

sistema de seguridad securOS

Uploaded by

Full Net
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
90 views9 pages

SecurOS System Specs v.2.7

sistema de seguridad securOS

Uploaded by

Full Net
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

SecurOS Server / Workstation Specifications

January 2022 New Jersey USA. ISS Engineering Department


v.2.7

INTELLIGENT SECURITY SYSTEMS


1480 US 9 NORTH, SUITE 202
WOODBRIDGE, NJ 07095

+1 732 855 1111 | www.issivs.com


Table of Contents:
Scope of Document 2
Section 1: SecurOS Operator Workstation Specifications 3
Section 2: SecurOS Video Server Specifications - VMS Cameras (SecurOS 64-bit version) 4
Section 3: SecurOS Video Server Specifications - ISS Analytics modules 6
Section 4: Windows Operating System Support 8
Section 5: Virtualization Support 8
Section 6: General Notes 9

Scope of Document:
This document is intended to help build a SecurOS server / workstation best suited for your system, in the case that the ISS Server line is
not being used. This document should be used as a guideline only. Values for camera counts, bitrate, fps, and resolution may vary
project to project and specifications should be adjusted accordingly. For CPU models mentioned in this document, it is not necessary to
use the same exact ones. CPUs with similar specifications can be used.

For additional questions please contact your local ISS Support Team.

2
SECTION 1: SecurOS Operator Workstation Specifications

Sample Specifications
RAM 16 GB (2x8GB) DDR4 3200 Mhz
# CPUs 1
Intel® Core™ i5-11600K
Sample CPU (12M Cache, 3.90 GHz) or better
6 Cores / 12 Threads
256 GB or more
OS Drive
(7.2K SATA, SAS, or SSD)
4GB NVIDIA Turing / Ampere (or
Graphics
better)
Network 2 x 1 Gb

Maximum simultaneous cameras viewed


Maximum cameras
Camera Details
viewed
H.264 / H.265 - 30fps
175 640x480 / 1.5Mbps
75 1280x720 / 3Mbps
56 1920x1080 / 4Mbps
H.264 / H.265 - 15fps
205 640x480 / 1.5Mbps
100 1280x720 / 3Mbps
71 1920x1080 / 4Mbps

SECTION 1 NOTES:
• SecurOS uses hardware capabilities of Intel® HD Graphics (with Intel® Quick Sync Video (QSV) 2.0 technology) as well as NVIDIA® graphics cards for decompression of H.264/H.265
video. To be able to view the amount of cameras specified above, one of these technologies must be used.
• Intel® QSV support for decompression of H.264 video, starts at 3rd Generation Core Processors; Intel QSV support for decompression of H.265 video, starts at 6th Generation Core
Processors.
• For supported NVIDIA® cards, refer to: https://developer.nvidia.com/video-encode-decode-gpu-support-matrix .
• DirectX 11 or higher must be installed on SecurOS Operator Workstations and Video Servers.
• The maximum number of cameras displayed can vary depending on the camera vendor used and the H.264/H.265 codec profile.
• If using older generation NVIDIA® cards (older than Turing / Ampere), then H.265 performance would decrease by 50%.

3
SECTION 2: SecurOS Video Server Specifications - VMS Cameras (SecurOS 64-bit version)

Low Capacity Sample Medium Capacity Sample High Capacity Sample


Cameras / Bandwidth (per 1 server) - SecurOS Motion Detection disabled
Max Bandwidth 350 Mbps 900 Mbps 1.7 Gbps 1
Max Cams 100 cams 300 cams 600 cams
Minimal Physical
2 4 8
Cores Required
Cameras / Bandwidth (per 1 server) - SecurOS Motion Detection enabled on 2nd camera stream (320x180)
Max Bandwidth 265 Mbps 675 Mbps 1.2 Gbps 1
Max Cams 75 cams 225 cams 450 cams
Minimal Physical
6 8 12
Cores Required
Cameras / Bandwidth (per 1 server) - SecurOS Motion Detection enabled on primary camera stream only
Max Bandwidth 175 Mbps 450 Mbps 850 Mbps 1
Max Cams 50 cams 150 cams 300 cams
Minimal Physical
6 8 12
Cores Required
Sample Specifications (per 1 server)
RAM 8 GB 16 GB 32 GB
# CPUs 1 1 2
Intel® Core™ i7-11700K Intel® Xeon Silver 4210 2 x Intel® Xeon Silver 4210
Sample CPU (16M Cache, 3.60 GHz) or better (13.75 MB Cache, 2.20 GHz) or better (13.75 MB Cache, 2.20 GHz) or better
8 Cores / 16 Threads 10 Cores / 20 Threads 20 Cores / 40 Threads
OS Drive 256 GB or more (SSD) 256 GB or more (2 x SSD - RAID1) 256 GB or more (2 x SSD - RAID1)

Recording Drive Type SATA SATA RAID5/6 NL-SAS RAID6/50/60

Minimal # Recording
1 6 10
Drives
2 x 1 Gbps /
Network 2 x 1 Gb 4 x 1 Gb 2 x 10 Gbps SFP+ /
2 x 10 Gbps Ethernet

1
Max recommended on 1 server or VM.

4
SECTION 2 NOTES:
• If running SecurOS on a virtual machine (VM), the ratio between physical cores and vCPUs should be 1:2. So for a 8 physical core processor, 16 vCPUs should be allocated.
For more information on running SecurOS on a virtual environment, refer to Section 5 of this document.
• The data above is assuming that no more than 2 SecurOS Operator Workstations (each with 2 physical monitors concurrently displaying 16 cameras) are connected to the
server. Systems with more than 50 SecurOS Operator Workstations will need a dedicated SecurOS Connection Server.
• If it is required to use a higher total bitrate or total amount of cameras per server, please consult with an ISS Pre-Sales engineer.
• Cameras connected to these servers will be used for video management purposes only (video streaming/recording/motion detection/etc… – no extra ISS
analytics).
• It is assumed that there will be NO local monitoring done from the video servers.
• Storage values above are sufficient for running Windows OS and the ISS software (they don't take into account video recording). For IP cameras, storage calculations can be
done using the ISS web System Design Tool or the IP camera vendor's storage calculator. For additional information about storage calculations please consult with the ISS Pre-
Sales Team.
• Network requirements above are generally sufficient to handle all the camera streams and up to 2 simultaneous client connections (each concurrently
displaying up to 16 cameras). For larger quantities of simultaneous client connections OR the use of a NAS storage, additional network cards might have to be
installed.

5
SECTION 3: SecurOS Video Server Specifications - ISS Analytics modules

Low Capacity Sample Medium Capacity Sample High Capacity Sample


Max Cameras (per 1 server) {Standard Performance | High Performance}
SecurOS Auto (Stop&Go) - US/ME 8 | 10 NA | 24 NA | 48
SecurOS Auto (Low Speed) - US/ME 4 | 6 NA | 12 NA | 24
SecurOS Auto (High Speed) - US/ME 2 | 3 NA | 6 NA | 12
SecurOS Auto (Stop&Go) - Other Regions 16 | 19 40 | 48 80 | 96
SecurOS Auto (Low Speed) - Other Regions 8 | 10 20 | 24 40 | 48
SecurOS Auto (High Speed) - Other Regions 4 | 6 10 | 12 20 | 24
SecurOS Cargo 8 | 10 20 | 24 40 | 48
SecurOS Transit 8 | 10 20 | 24 40 | 48
SecurOS Tracking Kit 11 | 13 27 | 32 54 | 64
SecurOS FaceX (Controlled) 4 | 6 10 | 12 20 | 24
SecurOS FaceX (Crowd) NA | 3 NA | 8 NA | 16
Sample Specifications (per 1 server)
Standard Performance1
RAM 16 GB (2x8GB) 2933MHz DDR4 64 GB (8x8GB) 2933MHz DDR4 64 GB (8x8GB) 2933MHz DDR4
# CPUs 1 2 2
Intel® Core™ i7-11700K 2 x Intel® Xeon Silver 4210 2 x Intel® Xeon Gold 5218R
Sample CPU (16M Cache, 3.60 GHz) or better (13.75 MB Cache, 2.20 GHz) or better (27.5 MB Cache, 2.10 GHz) or better
8 Cores / 16 Threads 20 Cores / 40 Threads 40 Cores / 80 Threads
OS Drive 256 GB or more (SSD) 480 GB or more (2 x SSD - RAID1) 480 GB or more (2 x SSD - RAID1)
3
Neural Net GPU Boost NVIDIA® RTX4000 NVIDIA® RTX4000 NVIDIA® RTX4000
Video Decompression GPU Boost4 Intel® Integrated Graphics NVIDIA® P1000 / T1000 NVIDIA® P1000 / T1000
GPU for SecurOS Auto CMM5 NVIDIA® P1000 / T1000 / RTX4000 NVIDIA® P1000 / T1000 / RTX4000 NVIDIA® P1000 / T1000 / RTX4000
2
High Performance
RAM 16 GB (2x8GB) 2933MHz DDR4 48 GB (6x8GB) 2933MHz DDR4 96 GB (12x8GB) 2933MHz DDR4
# CPUs 1 1 2
Intel® Core™ i9-11900K Intel® Xeon Gold 6242R 2 x Intel® Xeon Gold 6242R
Sample CPU (16M Cache, 3.50 GHz) or better (35.75 MB Cache, 3.10 GHz) or better (35.75 MB Cache, 3.10 GHz) or better
8 Cores / 16 Threads 20 Cores / 40 Threads 40 Cores / 80 Threads
OS Drive 256 GB or more (SSD) 480 GB or more (2 x SSD - RAID1) 480 GB or more (2 x SSD - RAID1)
Neural Net GPU Boost3 NVIDIA® RTX4000 NVIDIA® RTX4000 NVIDIA® RTX4000
Video Decompression GPU Boost4 Intel® Integrated Graphics 2 x NVIDIA® P1000 / T1000 2 x NVIDIA® P1000 / T1000
GPU for SecurOS Auto CMM5 NVIDIA® P1000 / T1000 / RTX4000 NVIDIA® P1000 / T1000 / RTX4000 NVIDIA® P1000 / T1000 / RTX4000

6
1
These are standard performance options that will work well with SecurOS Auto (Low Speed), Cargo, Transit, Tracking Kit, and FaceX (Controlled Scene 1-3 people) modules.
2
These are high performance options that will work well with SecurOS Auto (High Speed), SecurOS Auto (US/Middle East), FaceX (Crowd Scene 4-10 people) or FaceX used for access control
(single factor authentication). These scenarios require a higher performance per CPU Core.
3
Can be used to offload processing of additional cameras for SecurOS Auto (US/Middle East). Two cameras can be offloaded per 1 GPU.
4
Can be used to offload video decompression of the analytics cameras to the GPU. One GPU card for 25 cameras gives a 25% performance boost (so you can increase the number of cameras
supported on the server by 25% when using 1 GPU for every 25 cameras).
5
For the SecurOS Auto - Class / Color / Make / Model module, 1 of the supported GPU cards can handle 8 cameras (1 GPU per server can be used for this module, with the remaining cameras
being processed by the CPU).
6
For SecurOS Auto Stop&Go, set the camera fps to 1 / for Auto Low Speed, set the camera fps to 15.
7
For SecurOS FaceX (Crowd), it is recommended to use 1 x NVIDIA P1000 to offload video decompression to the GPU card (1 GPU for up to 25 cameras).
8
For standard performance servers, it is recommended to use 4 memory channels for 1 CPU; for high performance servers, it is recommended to use 6 memory channels for 1 CPU.
9
When selecting CPUs for Analytics Servers, it is recommended to use CPUs that support the Intel AVX-512 instruction set.

Number of Physical CPU Cores per 1 Camera


ISS Analytic Module # Physical Cores / 1 Camera Camera Details
SecurOS Auto (Stop&Go) - US/ME 1 Core / 1 Camera H.264 codec / up to 1080p resolution / up to 1fps
SecurOS Auto (Low Speed) - US/ME 2 Core / 1 Camera H.264 codec / up to 1080p resolution / up to 15fps
SecurOS Auto (High Speed) - US/ME 4 Core / 1 Camera H.264 codec / up to 1080p resolution / up to 30fps
SecurOS Auto (Stop&Go) - Other Regions 0.5 Core / 1 Camera H.264 codec / up to 1080p resolution / up to 1fps
SecurOS Auto (Low Speed) - Other Regions 1 Core / 1 Camera H.264 codec / up to 1080p resolution / up to 15fps
SecurOS Auto (High Speed) - Other Regions 2 Core / 1 Camera H.264 codec / up to 1080p resolution / up to 30fps
SecurOS Cargo 1 Core / 1 Camera H.264 codec / up to 1280x768 resolution / up to 30fps
SecurOS Transit 1 Core / 1 Camera H.264 codec / up to 1280x768 resolution / up to 30fps
SecurOS Tracking Kit 0.75 Core / 1 Camera H.264 codec / up to 1080p resolution / up to 30fps
SecurOS FaceX (Controlled) 2 Core / 1 Camera H.264 codec / up to 1080p resolution / up to 30fps
SecurOS FaceX (Crowd) 3 Core / 1 Camera H.264 codec / up to 1080p resolution / up to 30fps

SECTION 3 NOTES:
• If running SecurOS on a virtual machine (VM), the ratio between physical cores and vCPUs should be 1:2. So for a 8 physical core processor, 16 vCPUs should be
allocated. For more information on running SecurOS on a virtual environment, refer to Section 5 of this document.
• Cameras connected to these servers will be used specifically with the ISS Analytics modules: SecurOS Auto, Cargo, FaceX, Transit, etc…
• Using more cameras than the maximum specified in the tables above is not recommended.
• If using higher camera bitrates / resolution than specified above, please consult with an ISS Pre-Sales engineer.
• It is assumed that there will be NO local monitoring done from the video servers.
• Storage values above are sufficient for running Windows OS and the ISS software (they don't take into account video recording). For IP cameras, storage
calculations can be done using the ISS web SecurOS Design Tool or the IP camera vendor's storage calculator. For additional information about storage calculations
please consult with the ISS Pre-Sales Team.
• The data above is assuming that each camera is configured to send 1 stream to the ISS recording server.
7
SECTION 4: Windows Operating System Support
• Windows 8.1 Pro
• Windows 8.1 Enterprise
• Windows 10 Pro
• Windows 10 Enterprise
• Windows 11 Pro
• Windows 11 Pro for Workstations
• Windows Server 2012 R2 Foundation
• Windows Server 2012 R2 Essentials
• Windows Server 2012 R2 Standard
• Windows Server 2012 R2 Datacenter
• Windows Server 2016 Essentials
• Windows Server 2016 Standard
• Windows Server 2016 Datacenter
• Windows Server 2019 Essentials
• Windows Server 2019 Standard
• Windows Server 2019 Datacenter
• Windows Server 2022 Standard
• Windows Server 2022 Datacenter
* SecurOS Video Server can only be installed on a 64-bit OS. SecurOS Operator Workstation can be installed on 32-bit or 64-bit OSs.

SECTION 5: Virtualization Support


Supported VM Platforms:
• VMware ESX / ESXi 4.x, ESXi 5.1, ESXi 5.5, ESXi 6.0, ESXi 6.5
• Microsoft Hyper-V (on Windows Server® 2016 / 2019)
• Huawei Fusion Sphere

Notes about running SecurOS on a VM:


• The virtual machine should be built according to the standard SecurOS requirements for the specific task that is being performed (video recording, analytics, etc..).
• During calculation of the specs for the VM, always keep in mind how much resources (e.g. CPU) the host servers require to function. This point is miscalculated a lot, causing VM
Servers to have less recourses than were recommended.
• For best performance, the ratio between physical cores and vCPUs should be 1:2. So if 8 physical cores are required, then 16 vCPUs should be allocated.
• It is recommended that recording drives will be dedicated ones and not shared with many other VMs (so I/O is maximal).
• It is recommended that a VM use a dedicated physical NIC in place of a virtual one so all bandwidth is available.
• VMs configured for high throughput recording may see significant packet loss if not configured correctly. If packet loss is encountered you must check that no traffic filtering is
occurring, and secondly you must increase the number of buffers in the guest operating system (increase Small Rx Buffers and Rx Ring #1 Size to 1600 or higher). Refer to this article
for more information: https://kb.vmware.com/s/article/2039495

8
SECTION 6: General Notes
• For information about server specifications for ISS analytics modules not listed in this document please contact your local ISS Pre-Sales Team.
• It is possible to run SecurOS VMS cameras and SecurOS Analytics cameras on the same server. If your project requires this type of configuration, please consult
with your local ISS Pre-Sales Team.
• All new systems are sold with SecurOS version 11.X or higher.
• Information in this document is valid for SecurOS Professional, Premium, Enterprise, and MCC.
* ISS cannot guarantee the compatibility of the SecurOS software and other 3rd party VMS software on the same server.
** If using a NAS to record video/audio from a server running SecurOS, consult with the ISS Pre-Sales team for NAS interoperability.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy