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

Video Surveillance History on May 06, 2020
The video surveillance market has changed significantly since 2000, going...
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...
YOLOv5 Released Amidst Controversy on Jul 27, 2020
YOLO has gained significant attention within video surveillance for its...
Video Analytics 101 on Mar 16, 2020
This guide teaches the fundamentals of video surveillance...
Surveillance Storage 101 on Mar 23, 2020
This guide teaches the fundamentals of video surveillance...
Remote Network Access for Video Surveillance Guide on Jul 27, 2020
Remotely accessing surveillance systems is key in 2020, with more and more...
New Axis M30 Cameras Tested on Mar 26, 2020
Axis has released a new generation of, for them, relatively low cost M30...
Video Surveillance Cameras 101 on Feb 25, 2020
Cameras come in many shapes, sizes and specifications. This 101 examines the...
NetApp Video Surveillance Profile on Mar 09, 2020
NetApp is increasing its efforts in video surveillance and told IPVM...
Vehicle Gate Access Control Guide on Mar 19, 2020
Vehicle gate access control demands integrating various systems to keep...
Facial Recognition 101 on Mar 18, 2020
Facial recognition interest, use and fear is increasing. This guide aims to...
VSaaS 101 on Mar 25, 2020
Video Surveillance as a Service (VSaaS) is the common industry term for cloud...
VMS 101 on Mar 03, 2020
This guide teaches the fundamentals about video management...
Dynamic vs Static IP Addresses Tutorial on Apr 16, 2020
While many cameras default to DHCP out of the box, that does not mean you...
Facial Recognition: Weak Sales, Anti Regulation, No Favorite, Says Security Integrators on Jul 07, 2020
While facial recognition has gained greater prominence, a new IPVM study of...

Recent Reports

Google Invests in ADT, ADT Stock Soars on Aug 03, 2020
Google has announced a $450 million investment in the Florida-based security...
US Startup Fever Inspect Examined on Aug 03, 2020
Undoubtedly late to fever cameras, this US company, Fever Inspect, led by a...
Motorola Solutions Acquires Pelco on Aug 03, 2020
Motorola Solutions has acquired Pelco, pledging to bring blue back and make...
False: Verkada: "If You Want To Remote View Your Cameras You Need To Punch Holes In Your Firewall" on Jul 31, 2020
Verkada falsely declared to “3,000+ customers”, “300 school districts”, and...
US GSA Explains NDAA 889 Part B Blacklisting on Jul 31, 2020
With the 'Blacklist Clause' going into effect August 13 that bans the US...
Access Control Online Show July 2020 - On-Demand Recording of 45+ Manufacturers Presentations on Jul 30, 2020
The show featured 48 Access Control presentations, all now recorded and...
Face Detection Shootout - Dahua, Hanwha, Hikvision, Uniview, Vivotek on Jul 30, 2020
Face detection analytics are available from a number of manufactures...
Sunell is The First China Manufacturer to Market NDAA Compliance on Jul 30, 2020
Most China manufacturers are going to be impacted by the NDAA 'Blacklist...
Ink Labs Relabels China YCX Fever Camera And Steals Dahua's Marketing on Jul 30, 2020
A US company marketed a 'thermal temperature scanner' as its own, selling...
Genetec and Dahua-Backed Intelbras Split Examined on Jul 29, 2020
China is the cause of the breakup between Canada's and Brazil's largest video...
This YouTuber is Now Selling ThermoHealth Temperature Screening on Jul 29, 2020
An enterprising 20-year old is mass marketing medical devices on Facebook and...
Hikvision Returns To Growth Driven By Overseas Fever Cameras on Jul 29, 2020
While Hikvision's revenue fell in Q1 2020, it rebounded in Q2 attributed to...
Brazil's Biggest Domestic Surveillance Company Intelbras Profile on Jul 29, 2020
While Intelbras is not widely known outside of Latin America, Intelbras is a...
The Kiosk Market Pivots To Temperature Screening (Interviewed) on Jul 28, 2020
Video surveillance is not the only market that has pivoted to medical device...
Integrator Acquisitions 'A Good Market' During COVID-19, Says Greybeards on Jul 28, 2020
Industry broker Ron Davis of the "Greybeards" says that the integrator and...