Test *******
** *** *****, *********'* hardware ************ *********** ******* CPU **** **** ********* on ********* **** (**%+) or **** ***** ****** resolution *** ********* (**%+). Effects **** *** ** ***** when ***** ****** ********, with *** ***** *********** maxed ** ***% ****** our ** ****** *****.
*** ******* ** ****** on ****** *********** ******* improved ********* ** *** tests, ********* ******* ****** by *** ***** **% resolution *******, **** *** and *****. *******, ****** resolutions **** ****** ** more ***** ******* **** as ******* ***** *** artifacts ***** **** ** "motion", ***** *** **** to ***** *********** ** sensitivity ** *** ******** to **********.
Outlook *** *********
*** ******** ** ******** acceleration for *** *** *** potential ******** *** *********:
- ***** ******* *** ***** systems: ** ***** *******, hardware acceleration *** ****** *** number ** ******* ********, cutting hardware *** ***** *****.
- ***** *******/**** ********* *******: In ***** *******, ***** may ** **** ** run * ****** ******** of ******* ** ***** powered ******** (**** ** Intel ****/**** ***), ******** hardware ****, ******** ***** required, *** ******* ***** costs.
***** *** ********* ******** compared ** *********'* **** architecture.
*******, ***** ** *********, as **** ** ***********, may ****** *** **** further ** ***** ****** side ****** *********, ***** ********** the ********* **** ******** for ****** *** **********. Hardware ************ *** ** benefit ** ***** *********.
Our *****
** ****** ****** *********** using *** ********* *************:
- ***** **** **-***** @ 3.10 ***
- ***** **** ******** ****
- ** ** ***
- ******* ** *** ***
*********** *** ****** ***** 25 ******* **** ******* manufacturers, *** ********* ** 1080p, * ***** ** about **-** **/* ********** depending ** ********.
**** **** *** *** GPU **** ******* ***** refer **** ** ********* processes, *** *** ** as * *****, ** eliminate ********* ****** ** other *********.***-**** **** ** ******* GPU *****.
Default *** ******: *** ******* >**%
***** *********'* ******* *** settings (******** ****, **% resolution), *** ***** *** reduced ** **** **** half, **** *** **** increasing ** ********** (****** still **** ***).

High Resolution *********: *** **** ******* >**%
**** ********** ********** **** Milestone's **% *******, ******* are *** **** **********. For *******, **** ********* to ***% ********** (***** in ******* ******) *** analyzing ***** ****** (******), CPU ***** ** ******* from **** **% ** 8% **** ******** ************ on, **** **** * slight ******** ** *** usage. ********** ********* ********** has ***** ********/***** ********, detailed *****.

Faster ********, ******* ************
******** ************ ********** *** reduced **** ********** ******** speed, **** ** *********** to ******** ** *** tests.
*** *******, ********** **** keyframe **** ******** (~* second) ** ***** (***** as ****) ******* *** usage, **** **** ***** 80% ** **** ***** 50%, **** **** **** processing ********* ** *** GPU, ********** **** * baseline ** ~*% ** 28%.
******* **** ********** ******** speed ******* **** **** less, ******** *** **** from * ******** ***% to **%, **** **% CPU ****.

Accuracy ******
** *** *****, ****** from ******* **% ********** to ***% *** * significant ****** ** ***** and ********, **** ******** able ** ****** ******* using **** ********** ***** were *** ******** ***** lower ********.
*** *******, ** *** scene *****, *** ******* walking ** ~**' ***** (~10 ***) ** *** detected ***** ******* **% resolution. *******, ********** ** 100% (*****), *** ******* is ******** ***** ****. *** same *** **** ** low ***** ****** (****** notably ******* **** **').
False ********** ******** **** ****** ********** *********
*******, **** ********** ********* resolution, ***** ****** ********* set ********* *** ***********, as ****** *********** "***" more ******* **** *** default **%.
*** *******, ******* ** the **** ***** **** no ******** *******, ** the **** ** **% resolution, **** ** ******* detected **********. *******, ** the *****, ***** ***% detection, **** ***** ***** are *********** ** *****, as ***** *******, ******* noise, *** *********** *** shown.
Hardware ************ *************
***** ** ****** ************* required *** ******** ************. Users ****** ****** * single ****** ** "*********" instead ** "***" ** VMD *****. ***** ** no ************* ***** *** hardware *********** ***, *** guidelines *** ********* *******, updating *******, ***., *** the **** ** ***** in ***** ***** ****** ******** ************ Quick *****.

Xprotect *********/****** ****
******** *********** *** ** available **** ** ******** Corporate *** ******, ** other ********, *** ** their ********* ********. ***** of ************, **********, ***., must ******* ** **** wish ** **** ********* of **** *******.
QuickSync *************
*** ******** ************ ********* ************* *********. ********* ******** ***** will **** ** ******.
*** ********* ******* *** be ************* **** ******* **** Intel. **** ******* *** server ********** *** *********, though ******* ** **** common ** ******* ******. Note **** ********* ** an ***** *******, *** is *** ***** ** AMD **********.
********* **** ********** **** the ****** *** * "balanced ******" *** **, with *** ** **** DIMMs, *** **** *******. For *******, ** * server *** *** ****** slots, ***** *** ******* are ***********, ******* ** a ****** *** ****.
Versions ****
******* *** ********* *****:
- ********* ******** ********* **** R1: **.**
- ****** **** *.**
Comments (19)
Donald Gordon
Thanks for the report Ethan. Prior to this feature, we had to use camera-side VMD which works good enough but probably not as good as the server-side VMD. It would be nice to see a report comparing server-side VMD to camera-side VMD. At lot of camera manufacturers seem to offer VMD now. With that in mind, you can purchase a much cheaper recording server and offload the VMD to the cameras (if you even need VMD processing).
You probably saw the recent announcement from Milestone that they are teaming with NVidia to use the NVidia GPU to perform the hardware acceleration. This should be interesting. We hope this feature is extended to the Milestone Smart Client video decoding which is currently our performance bottleneck.
Don
Create New Topic
Mike Dotson
Good report Ethan. I would like to add a little to the info.
We still see many customers request Windows7, and this OS does NOT support QSYNC. Only Win8 and newer OS versions do.
For the Professional and lower code versions, the QSYNC will also get used by the 'Mobile Server' service according to the documentation.
"If the processor on the mobile server supports hardware accelerated decoding, it is by default enabled"
This service is 'transcoding' a video stream wherever it is running. One has to be aware of this load because it can easily swamp an underpowered CPU and the primary recording function will get swamped.
Fortunately, one can install this service on a separate system.
Also note this limitation: "Hardware-accelerated decoding is not supported, if the mobile server is installed in a virtual environment."
This is simply a reflection of the fact that ESX currently does not support the integrated GPU.
Create New Topic
Undisclosed #3
Question, were the following tests all using keyframe only?
Create New Topic
Ethan Ace
Note: we removed "GPU" from parts of the test (including the title) to avoid the impression that this hardware acceleration was effective using a separate hardware GPU (e.g., Nvidia). QuickSync offloads processing to a "GPU", but it's actually a specific CPU architecture function, not a dedicated GPU.
However, if you use a tool such as GPU-Z (below, from our tests) to measure load, QuickSync load does show as GPU load:
Create New Topic
Vincent Tong
So basically milestone found a way to make up for their inefficiencies on the CPU usage on the VMD server side. Reminds me of Blue iris in a way of cpu load for vmd.
They could have just done it more efficient similar to how NX Witness has been handling VMD server side with such a minimal CPU load for all these years. So in a way i figure it is more of a band aid by throwing other technologies or brute force by handling the load.
Create New Topic
Marcelo Martinez
07/19/17 08:27pm
Hi John, good article, even when them camera market is moving to >4MP & H265.
Do you believe more capture compression, needs more processing to get acceptable results ?
Good opportunity to talk about servers, storage & workstation performance with a same camera set. At the end of the road, this balances is what the end user get form a middle to large systems.
Create New Topic