Risks of Overloading Video Surveillance Systems

By John Honovich, Published on Mar 29, 2009

Cameras, software and recorders are all becoming more powerful and complex. Higher resolution, multiple streams, multiple analytics and more powerful CODECs greatly enhance the potential of video surveillance. At the same time, using multiple features together can routinely overload a video surveillance system, creating significant problems that are hard to resolve.

Traditional Video Surveillance - Simple but Limited 

In the old days, you had analog cameras and DVRs - both of which were very limited in what they could do. Because they were so limited, it was hard to misconfigure or overload the system. A recorder only had so many inputs and an analog camera could only send a single fixed stream.

The Claims of Today's Video Surveillance

Today's video management systems and cameras can use H.264, can handle multiple megapixel streams and run on-board analytics on video. It is becoming very common for companies to market all of these advantages.

The Problem for Users

The problem is that it is almost impossible to run all, or even many, of these functionalities at the same time. Making the problem worse, this is generally only disclosed in the fine print or footnotes of the marketing material.

Users and integrators need to be careful about designing systems with these products. 'Optimistic' designs based primarily on vendor marketing can deliver systems that significantly under-deliver or break down in real world use.

Recording both IP and analog cameras is a key claim for hybrid DVRs. The critical question is: how many IP cameras and at what resolutions and CODECs can this be done? While a hybrid DVR may record 12 IP cameras at MPEG-4 with CIF resolution, it may not be able to record even a single 3MP camera using H.264.

A similar concern exists with video analytics. Running video analytics inside of the DVR offers a lot of potential. The challenge is knowing how many channels of video analytics and what type of video analytics can be run.

Get Notified of Video Surveillance Breaking News
Get Notified of Video Surveillance Breaking News

The more video analytics you use, the less IP cameras you may be able to support. Plus, the more activity on your cameras, the less you may be able to manage as well.

While there are clear benefits for using hybrid DVRs, there are risks as well.

IP Camera - Example

IP cameras are more frequently being marketed as platforms that can send multiple streams, use multiple CODECs and run a variety of video analytics.

Just like with hybrid DVRs, the problem is you cannot do all of these at once.

More critically, a growing belief exists that any IP camera can be a smart camera. Many IP cameras can have some smarts but almost all IP cameras on the market are quite limited in how 'smart' they can be. Agent VI [link no longer available] is one popular approach of taking existing IP cameras with moderate "horsepower" and adding video analytics. However, Agent VI still requires additional server side processing. This does not make it bad. You simply need to be aware of this in your designs. Via:sys [link no longer available] does claim to run solely on existing Axis and IQinVision cameras but you should be extremely careful about its level of false alerts and how it can perform in adverse environments.

IP Video Surveillance Software - Example

One of the most attractive claims of using IP Video software is that you can greatly expand the number of cameras you can record on a given server.  Unlike cameras and hybrid DVRs, you also can choose your own hardware to optimize it for a given load.

Even with this flexibility, you need to be careful about the settings of cameras used. While vendors often talk about recording hundreds of cameras per server, they usually mean standard definition cameras using MPEG-4 and only motion detection. Once you start using multi-megapixel cameras, H.264 CODECs and video analytics, the number of cameras per server can drop dramatically.

Why does this problem exist?

Manufacturers are careful to keep costs as low as possible to remain competitive. For instance, IP cameras and hybrid DVRs could support far greater loads if the manufacturers used faster processors, greater memory, etc. The trade-off is that this costs more money and would force the manufacturer to increase the price of the product significantly. Most manufacturers have decided that the best route is to keep costs low at the expense of greater complexity and risk of overloading. (I agree with this.)

Over time, as computing resources become cheaper relative to the growth in video surveillance technologies, manufacturers will no longer face this trade-off and the problem will be resolved. However, for the next few years, given the explosion in resolution and the demands of video analytics, system designs must carefully factor in this trade-off.

What symptoms or issues will occur?

The risks are similar to that of over-loading your PC with too many applications. When you have too much running, the PC can become much less responsive, if you are watching a video, the video may stutter and eventually your PC may lock up. Since cameras and recorders are computers, it's not surprising that they are impacted in a similar ways as to PCs.

The specific video surveillance risks are:

  • Frames may drop. Even if you set the frame rate for 15 frames per second, the camera may only be able to send 8 frames or the recorder may only be able to record 7 frames, etc.
  • Video analytics may miss events (false negatives). Dropped frames may cause the video analytics not to catch an event.
  • The recorder or camera may become very slow or unresponsive. If you do a search or request video, the system may not be able to deliver as it is blocked by other processes already running.
  • The system may crash or need to be manually rebooted.

How do I determine how much load a system can handle?

After reviewing this topic with over a dozen vendors, manufacturers have very little clarity on how much load a system can handle. Most sales or marketing people know very little about the specific issues or constraints involved. Often, even system engineers are not sure about the details.

Part of the problem is that this issue is fairly new as it reflects new technology released only in the last few years. The other challenge is that load depends on a variety of factors.

Before you design a system and buy products, you should carefully review your configuration with the manufacturer. You need to provide:
  • Resolution of each camera
  • Frame rate of each camera
  • CODECs of each camera
  • % Motion activity on each camera
  • Number of channels of video analytics being run
  • For cameras, how many streams being used

Specifically, you should be careful about megapixel streams and video analytics - both can take huge amount of resources and can place significant constraints relative to the marketing claims presented.

How can I check load once the system is deployed?

This can be quite difficult because it depends on the tools provided in the products you are using. In cameras and hybrid DVRs, you are dependent on what the manufacturer provides you. In most of these products, there are little to no tools that report on load.  With IP video surveillance software, even if the software does not provide you tools, you can use standard monitoring applications provided with the OS.

The best way to solve this problem is by a careful up-front design. Beyond that, to the extent you can monitor load in deployments, you will reduce the risks of problems arising. In the future, I believe (or hope) vendors will provide more pre and post sales tools to minize the risks in deploying more advanced and powerful solutions.

Related Reports

Bandwidth Fundamentals For Video Surveillance on Jan 13, 2020
Bandwidth is the most fundamental element of computer networking for video...
AI Video Surveillance (Finally) Goes Mainstream In 2020 on Sep 03, 2019
While video surveillance analytics has been promoted, hyped and lamented for...
Video Surveillance Cameras 101 on Feb 25, 2020
Cameras come in many shapes, sizes and specifications. This 101 examines the...
Video Analytics 101 on Mar 16, 2020
This guide teaches the fundamentals of video surveillance...
Converged vs Dedicated Networks For Surveillance Tutorial on Feb 12, 2020
Use the existing network or deploy a new one? This is a critical choice in...
Axis Door Station A8207-VE Tested on Aug 07, 2019
Axis newest door station, the A8207-VE, claims to deliver "video...
Remote Network Access for Video Surveillance Guide on Jul 27, 2020
Remotely accessing surveillance systems is key in 2020, with more and more...
Directory of 30+ VSaaS / Cloud Video Surveillance Providers on Jun 07, 2019
This directory provides a list of VSaaS / cloud video surveillance providers...
Verkada Video Quality Problems Tested on May 23, 2019
Verkada suffers from numerous video quality problems, not found in commercial...
Surveillance Storage 101 on Mar 23, 2020
This guide teaches the fundamentals of video surveillance...
YOLOv5 Released Amidst Controversy on Jul 27, 2020
YOLO has gained significant attention within video surveillance for its...
Covert Elevator Face Recognition on Oct 24, 2019
Covert elevator facial recognition has the potential to solve the cost and...
Quantum Dots Potential for Surveillance Cameras Explained on Sep 08, 2020
Quantum dots are starting to be used in TVs for better images, but how will...
Video Surveillance History on May 06, 2020
The video surveillance market has changed significantly since 2000, going...
2020 Video Surveillance Cameras State Of The Market on Jan 03, 2020
Each year, IPVM explains the main advances and changes for video surveillance...

Recent Reports

GDPR Impact On Temperature / Fever Screening Explained on Oct 22, 2020
What impact does GDPR have on temperature screening? Do you risk a GDPR fine...
Security And Safety Things (S&ST) Tested on Oct 22, 2020
S&ST, a Bosch spinout, is spending tens of millions of dollars aiming to...
Nokia Fever Screening Claims To "Advance Fight Against COVID-19" on Oct 22, 2020
First IBM, then briefly Clorox, and now Nokia becomes the latest Fortune 500...
Deceptive Meridian Temperature Tablets Endanger Public Safety on Oct 21, 2020
IPVM's testing of and investigation into Meridian Kiosk's temperature...
Honeywell 30 Series and Vivotek NVRs Tested on Oct 21, 2020
The NDAA ban has driven many users to look for low-cost NVRs not made by...
Avigilon Aggressive Trade-In Program Takes Aim At Competitors on Oct 20, 2020
Avigilon has launched one of the most aggressive trade-in programs the video...
Mexico Video Surveillance Market Overview 2020 on Oct 20, 2020
Despite being neighbors, there are key differences between the U.S. and...
Dahua Revenue Grows But Profits Down, Cause Unclear on Oct 20, 2020
While Dahua's overall revenue was up more than 12% in Q3 2020, a significant...
Illegal Hikvision Fever Screening Touted In Australia, Government Investigating, Temperature References Deleted on Oct 20, 2020
The Australian government told IPVM that they are investigating a Hikvision...
Panasonic Presents i-PRO Cameras and Video Analytics on Oct 19, 2020
Panasonic i-PRO presented its X-Series cameras and AI video analytics at the...
Augmented Reality (AR) Cameras From Hikvision and Dahua Examined on Oct 19, 2020
Hikvision, Dahua, and other China companies are marketing augmented reality...
18 TB Video Surveillance Drives (WD and Seagate) on Oct 19, 2020
Both Seagate and Western Digital recently announced 18TB hard drives...
Watrix Gait Recognition Profile on Oct 16, 2020
Watrix is the world's only gait recognition surveillance provider IPVM has...
Intel Presents Edge-to-Cloud Ecosystem for Video Analytics on Oct 16, 2020
Intel presented its processors and software toolkit for computer vision at...