Skip to content

Calculating disks and network load for video surveillance

Network sizing is based on transmitted streams; archive capacity is based on recorded data and retention. Check disk performance with simultaneous writing and reading. These limits are checked separately: sufficient capacity does not guarantee sufficient speed.

The formulas below use decimal units: 1 Mbit/s = 1,000,000 bit/s, 1 MB = 1,000,000 bytes, 1 TB = 10¹² bytes. There are 8 bits in a byte. GiB and TiB values displayed by some utilities use powers of 1024 and will be numerically smaller for the same byte count.

Network load

Incoming traffic is the sum of bitrates of all sources received by the streamer. If it receives both a main stream and a substream, count both. Also measure peaks for variable bitrate.

Outgoing traffic depends on the number of simultaneously open streams. A viewer with a four-camera mosaic creates four views. Add archive exports and inter-server transfers separately, including backup copies if used.

For identical streams:

Input, Mbit/s = number of received streams × bitrate of one stream
Output, Mbit/s = number of simultaneous views × bitrate of the viewed stream

For different cameras, add their bitrates. Multiply the result by your chosen design reserve factor. For example, a 30% reserve means a multiplier of 1.3; this is a calculation assumption, not an automatic Watcher limit.

Check interface direction and network characteristics. Placement also takes total network load into account; specify the measured bandwidth in the streamer settings.

Disks

For continuous recording of one stream:

Archive, bytes = bitrate, bit/s × retention, s / 8
Daily archive, GB = bitrate, Mbit/s × 10.8

Thus a 1 Mbit/s stream produces 10.8 GB per day before additional data and reserve. For multiple streams, add the volumes, accounting for the number of stored copies and actual recording mode. Additional episode retention and separate streams increase usage.

To determine purchased capacity, divide the calculated volume by the fraction of the disk you plan to use. For example, a design limit of 90% gives a divisor of 0.9. Do not treat a value from someone else's example as a universal fill limit: check DVR settings and required free space for your installation.

Retention is set in seconds through expiration. Additional episode retention may preserve part of the archive longer. Byte and disk-fill limits also affect cleanup; configured depth does not guarantee that retention when capacity is insufficient.

To check speed, add writing and expected archive reading. Divide by 8 to convert Mbit/s to MB/s. Compare the result with speed measured on your filesystem under the same operation mix. A disk's specified sequential speed does not describe many simultaneous reads from different cameras.

For root and disk list configuration, see streamer DVR. Distributing data across disks does not itself create another video copy.

Example

Suppose the project has:

  • Cameras — 500 recorded streams at 1 Mbit/s each.
  • Views — 200 simultaneous streams at 1 Mbit/s each.
  • Retention — 7 days, or 604,800 seconds.
  • Reserve — 30% added to calculated traffic and volume.
  • Fill — no more than 90% of purchased capacity is to be used.

Result:

Input with reserve = 500 × 1 × 1.3 = 650 Mbit/s
Output with reserve = 200 × 1 × 1.3 = 260 Mbit/s
Data for 7 days = 500 × 1 000 000 × 604 800 / 8 = 37.8 TB
Data with reserve = 37.8 × 1.3 = 49.14 TB
Purchased capacity = 49.14 / 0.9 = 54.6 TB

For disk verification in this example, writing with reserve is 81.25 MB/s. If all 200 views read from the archive, another 32.5 MB/s of reading is added: a total of 113.75 MB/s before other storage operations.

This calculates load without specifying a suitable disk count. Choose an array that provides the capacity and handles the measured mix of writing, reading and cleanup simultaneously. Then check for recording gaps under the required load.

Calculating stream and view counts from disk performance

A reverse calculation is possible when verified storage performance is known. With identical bitrate B and reserve factor k:

Recorded streams + archive reads ≤ 8 × P / (B × k)

Here P is measured mixed speed in MB/s, and B is one stream's bitrate in Mbit/s. Live views do not always read disks, while archive exports may run faster than the original bitrate, so account for actual operations.

This formula's result is limited by disks. Check CPU, network and streamer failure reserve separately.