Hikvision Web Client Poor Performance Question

Hey guys,

This may be for some of the more technical users out there. But one of our client end users has a newer (1 year old) Hikvision system installed. I noticed that when on-site using the native Hikvision viewing client (iVMS-4200 V2.6.2.7) the performance on an older computer is decent. Even when live viewing up to 16 cameras the computer is using only a small fraction of the 3 gHz total processing power and 2.5 of the total 4 GB of Ram.

But when I access the same NVR through the web client when off-site the live view of the same 16 cameras pegs my 4 gHz processor and uses about the same memory. Does anyone know what causes the drastic difference in processing power used? Is it because I am using Chrome to access the web client? Is it an internal NVR setting? If anything I would have expected my memory to take the increased hit and not the processor.

Login to read this IPVM discussion.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

** *** *** ***** *** *** ******-**** *** ******* ******* method, *** * ** ******* **** **** **** **** ********** power. *** ******* ** ** **** ******* ** *** ** that ******* *** **********.

****** ****, ** ****** ***** *** ** **** ** **** may ** *** *****. * **** **** ****** *** ****** increasingly ******* ******** *** **** ** *** *** ************ **** better ** ****** **** ******** ****. * *** *** ** for **** ** ***** ** ***********. ****** *** *** ****.

**'* ****** **** *** ******** ***** ***** **********, ******* ** Axis. ** *** **** **** *********** ***** ******** ** *** browser **** ** ********* **** ************************ *** **** ***********.

***** *** ****,

*****

****** *****, * **** ******* ******** **** ** *** ** avoid *** ****** ******. *** * *** ****** **** ***** the ********* *** ****** *** * *** **** ***** ********** a *** ******. * *** ********* ** *** **** ***********.

****** **** **** **** *. ******. *** ****** ******* ** the ****-** *** *** ***** *** ** * **** ******** hog.

**** *** ** *** *** **** *** **** ** * try.

[****** ******/******** *******]

********->****** **** ** ********, **** ****** **** ** ******.

******* - *** ******** ************ **** *********. /******** *******.

**** ****!

******, * *** **** **** * ***.

** ***'* *** *** *** ** *********** *** **** ***** a ****** ***** *** **** * ***** ******. *** ******'* IT ********** ***** *** *** ** ******* ***** ***, *****' client ********. **** ***** *** *******, ** ****** *** *******. When **** ******* ** ** ******* *** ******, ** *** so **** ******. *** **** ******'* ***** *** ******** ** remain ** **** ******** ****** * ****** ** **** *** the ****** ********.

** *** *** **** ** *** ****** ** **** ** anything ***** **** ******* ** ** *** ** *** ****** to *******, ***'* ***.

*** *** ***** **** ***** *** *** ****** ** **** video *** ****** *** ************ ** *** *** *** ***** is *******. **** ******* *** **** ** ***** **** ************* with *** *** *******. *** ***** **** **** ** ***** are ** ********* **** ** ******* ****-**** *********** ***** ***** protocols. * *** ** ******** ** **** *** ***** ******* the ****** *** ****** ** ****** * **** **** **********. It ** *** ******** ** ***** *********** **** *** ***** a *********** **** ** **** ********'* *********. **** ***** * native ****** **** *** *** *** ***** ******* ** *******, the ********** *** ***** *** ******* ***********. **** **** ***** saying, ******** ************ ******** ** **** *** ******** *** ****. In *** **** ** ****** *** ***** **** *** ************ if *** ****** *********** *** * ****** ****** ******** ****. One ** *** *** **** ** *** ********* ****-**** ***** through * *** ******* ** ** *** *** *** **** websockets. **** ** * ********** **** ** ********* ******* ***** such ** *** ****** *********** *** ********. ***** ********* ******* produce ************* **** ******** **** *** ********* ****/***** ******** **** by ****/*** *** *******. ***** ** * **** ******* *** can **** ** ** *** *** ********** ** ******** **** about *** ********** **********. *****://*********.***/*******.**** . **** ** ***** ** be ************* ** *** ******** ** **** ******** ******* ***** it ******* ** *** ***** ****** ** ********** *****. *** other ******* ** *** ***'* **** ** *** ***** ***** plugins ***** **** ** **** **** ** ******** ******** ***** brings **** ** * **** ** ************* ******.

*** ** **** ** *** **** *** *********.

*’* ********* ** *** *** ****** ** ****** **** *.*** encoding *** *** ***** ****** **** *.*** ********?

** *****'* **** **** ******, *******, *** ******** ******* ****(*.***). I **** **** **** ***** ***** *******. **** ** **** an ***** **** ** ***** ** ***** ****. **** *** patent *** ******* ****** ***** *** **** ** ********* *** the *** ******** ** ****** ***** ** ** **** *** with *.***.

****,

***

**** *********** ******** *** *********