Maximum Numbers of Cameras in the MxMC

Maximum number of cameras that can be simultaneously displayed in one or more grids with the MxMC, so that

  • the presentation is still fluid without video jitter and
  • the user interface of the MxMC still reacts fast enough to user input.

Performance values have been verified with following components and settings:

  • MxMC 1.5
  • 108 different P3 cameras Firmware 4.4.2.69 and following settings:
    XGA, 60% JPEG-Quality, MxPEG
    Image Quality „normal“
    Max. exposure time = 1/30s

-> The above settings lead to an average data-rate of about 2.5 MBit/s per camera.

Result on different systems:

Mac Pro, 2x Dual-Core Intel Xeon, 2.66GHz, 5GB RAM
– Win 7 Ultimate (64bit): 45 cameras
– Mac OS X 10.7:
- OpenGL activated (=Default): 35 cameras
- OpenGL deactivated: 45 cameras

Mac Pro, 12 Core Intel Xeon E5 (Hyper-Threaded), 2.7GHz, 16GB RAM
– Win 8.1 (64bit): 120 cameras !
– Mac OS X 10.10:
- OpenGL activated (=Default): 80 cameras
- OpenGL deactivated: 120 cameras

Important to know:

  • Key criteria for display and number of cameras that can be displayed in parallel is the total number of frames per second, that MxMC has to decode and display.

  • The Selection of different codecs (M-JPEG or MxPEG) has minor influence, as in both cases always full-frames are displayed. As a result, the bottleneck using Multicore systems is the displaying part (see next point).

  • Decoding of the different video-streams always is executed within different threads (1 thread per stream) and therefore performed on different CPU-cores. Displaying all the decoded streams on the monitor and the processing of all User-Events is executed in the single „Main Thread“ and as such always in one single core. When using Multicore systems (as the one described above with 12 resp. 24 CPU-cores) the single CPU core performing the Main Thread leads into a bottleneck when exceeding a certain number of cameras whilst all other CPU cores may still be underutilized.

  • Codec setting primarily influence the resulting stream data-rate. Especially when using Mx6 cameras with M-JPEG or MxPEG with huge Motion Ratio in the scenery, a data-rate of
    20 MBit/s and more can be reached easily. When using up to 50 cameras in that case the overall network data-rate may reach the 1 GByte network limit.
    The memory need of MxMC with above tests using 120 cameras was about 1.2 GByte

-> As a result we recommend a system with not so many (i.e. 8) but fast CPU-cores (e.g. >= 3GHz)

2 Likes

Typical PC hardware that meets the requirements high CPU rate and few cores
1. For normal use up to approx. 16 cameras
Dell OptiPlex 3050 Micro Form Factor
(N002O3050MFF)

2. for higher requirements with two monitors 25 cameras per monitor
Dell OptiPlex 3050 Small Form Factor XCTO

3. requirements going beyond this and requiring up to four monitors (assuming 25 cameras per monitor with 12 fps)
HP Z2 Tower G4 Workstation
or
DELL Precision 3630 Tower

**To connect 4 Monitors you require a extra graphic card **
for example the:
Radeon™ Pro WX 4100 Graphics

When using H264 streams you have to consider that the H264 codec needs much more computer performance compared to MxPeg. This has to be taken into account when configuring the project.
12 cameras with 1280x960 are executable on a PC with the following equipment:
DELL Precision 3630 Tower

H264 hardware decoders are not supported by the MxMC.

A Hardware example from a Retail Project:

MxMC 2.1.2:

  • One Layout
  • 25 x MOBOTIX P26
  • Resolution Full HD @25 fps
  • 5 Layouts with each 25 cameras

Hardware Specs:

  • Intel i5 6-Coee 9400T @3,4 GHz
  • Onboard CPU Graphic
  • SSD 256 GB Ram
  • 8 GB Ram
  • 27" Full HD Screen
  • Windows 10

The Live Streams are running smoothly without performance issues.

Hardware Requirement

#########
GERMAN

Hardware Anforderung: