Testing Bandwidth vs Frame RateAuthor: Benros Emata, Published on Aug 30, 2011
*****PLEASE NOTE: DUE TO THE AGE OF THIS ARTICLE, WE WILL RE-RUNNING THIS TEST AND UPDATING IT IN APRIL 2018.*****
Frame rate selection has a major impact on bandwidth consumption for surveillance cameras. While most cameras have a maximum frame rate of 25 to 30 frames per second, users typically choose significantly lower frame rates, driven by a desire to minimize storage consumption. The most direct way to reduce storage is to use a lower bit rate stream for each camera with lower frame rates.
A key practical question is how much bandwidth is saved as the frame rate is dropped? Lower frames rates should result in lower bit rates but how significant are those changes and does this change depending on the scene?
In this report, we share our result of a series of experiments we did with 3 IP cameras (Avigilon, Axis and Sony) in 3 different scenes: (1) indoor daytime, (2) indoor dark (< 1 lux), and (3) daytime outdoor (intersection). We did tests at 1, 5, 10, 15 and 30 fps to see how bandwidth consumption varied across a variety of frame rates.
We then produced a series of charts comparing bitrate vs frame rate and average frame size vs frame rate to provide two views on the relationship between these parameters.
With these test results, we answer the following questions:
- How does bandwidth efficiency vary with changes in the frame rate?
- Are low frame rate streams inefficient?
- How can you project bandwidth consumption for various frame rates?
- Does different scene types impact bandwidth vs frame rate efficiency?
- How does the choice of VBR vs CBR impact the relationship between bandwidth and frame rate?
For background on frame rates, Pro members should review our frame rate fundamentals training. Also, for those interested in understanding the impact of bandwidth, review our sister report that examines the relationship between bandwidth and image quality.
Key Findings and Recommendations
- Bandwidth efficiency of lower frame rates can be modestly less efficient than higher frame rates when the I frame interval or scene complexity is low
- As the scene becomes more complex (e.g., nighttime, noisy scene), bandwidth increases rather linearly as frame rate increases
- No 'massive' bandwidth penalties exist for low frame rate H.264 encoding
- Figuring out the right bitrate for a CBR camera at different frame rates is hard
- Unless your scene is quite simple (e.g., indoor office), you can ignore the impact of short I frame intervals or low frame rates impacting bandwidth efficiency
- Even in simple scenes with short I frame intervals, bandwidth consumption is not a real concern as the bitrate will be quite low regardless (either very low or very very low)
- When estimating bandwidth, using a fixed image size is generally a fair approximation but be careful because results could be off by up to 50% of projection.
- When using CBR, if possible, try running in VBR mode first to get a baseline bandwidth level and use that as your CBR setting. Alternatively, export a few sample clips at different CBR bit rates, run this in a stream analyzer and pick the bit rate that results in a DRF of 32 or less
VBR Indoor Daytime (Low-Complexity)
In this indoor daytime scenario the scene is fairly non-complex. Both cameras operate at VBR, but differ in their I-frame intervals. The Avigilon is using a 1s I-frame interval, whereas the Axis generates an I-frame for every 32 frames.
Bitrate vs. Frame-Rate
The Axis camera is considerably more efficient at the lower frames than the Avigilon camera. This is largely because the I-frame interval is effectively higher in the Avigilon at lower frame rates (at 1fps the ratio of Avigilon to Axis I-frames is ~30:1). At approximately 10fps the bitrates of the two cameras converge despite a 3:1 I-frame ratio. Another key point that may not be so obvious from the shape of the curves, is that bitrates increase less than linearly. As such efficiency improves at higher frame-rates (especially the Avigilon, which uses a per second I-frame interval).
Average Frame Size
At the lower frame rates the inefficiency of the higher I-frame interval is quite apparent. The Avigilon curve (red) indicates a considerable cost (in bytes) for I-frames relative to P-frames. This discrepancy is characteristic in less complex scenes, where P-frames are relatively efficient to produce (<10KB). The two curves converge around 10fps at roughly 10KB. The curves both continue to descend to a minimum at 30fps to ~7KB. At 30fps P-frame sizes dominate the average frame size metric (~30:1). With a value of ~7KB it suggests a low complexity scene and high compression efficiencies.
VBR Indoor Nighttime (High-Complexity)
In this indoor nighttime scenario the scene is highly complex due to the presence of noise/gain. Both cameras operate at VBR, but differ in their I-frame intervals. The Avigilon is using a 1s I-frame interval, whereas the Axis generates an I-frame for every 32 frames.
Bitrate vs. Frame-Rate
At the low frame-rates the I-frame intervals between the two cameras are most significant. For example, at 1fps the Avigilon produces one I-frame for every one P-frame (or 1 every second), and the Axis camera produces one I-frame for every 31 P-frames (or 1 every 31 seconds). As such we would expect to see divergence of bit-rates at these lower frame-rate levels, but this is not the case as the curves follow each other in near identical fashion. It is clear that compression efficiency is very low due to the complexity level of the scene and that byte-wise cost of P-frames is not much 'cheaper' than I-frames, as a result. A key feature of these curves is the linear relationship between bitrate and frame-rate, suggesting no clear frame-rate where efficiency is at its greatest.
Average Frame Size
The minimum frame sizes of the two cameras of ~25KB to ~30KB is considerably higher than the ~7KB minimum found in the non-complex indoor daytime scene. The most interesting feature of this graph is the relative flatness of the Avigilon (red) curve. Because the Avigilon average frame size is influenced strongly by I-frame size at lower frame-rates and by P-frame sizes at higher frame-rates, its curve indicates the relative sizes of I vs. P frames. Given that the curve is mostly flat suggests little material difference between I and P frame sizes. This is characteristic and somewhat expected in highly complex scenes. As a result there is no clear frame-rate that is most efficient and as the previous graph depicts bitrates increase rather linearly as frame-rates are increased.
VBR Outdoor Intersection (Moderately High Complexity)
In this busy intersection scenario the scene is moderately high in complexity. Both cameras operate at VBR, but differ in their I-frame intervals. The Avigilon is using a 1s I-frame interval, whereas the Axis generates one I-frame in every 32 frames.
Bitrate vs. Frame-Rate
As in the highly complex nighttime scenario, the curves of the two cameras provide no clear area or point of divergence. Their bitrate values are actually quite similar at each frame-rate setting. The bitrates reach a high of ~4mbps at 30fps, which is considerably lower than ~6.5mbps high observed during the very complex nighttime scene. This tends to suggest a somewhat lower level of complexity than the night scene.
The shape of the graph tends to flatten out going from lower to higher frame-rates, suggesting some efficiency gains at the higher P-frame saturated frame-rates.
Average Frame Size
As expected the Avigilon camera, which uses a 1 per second I-frame interval, exhibits a sharper decline in average frame size as frame rates increase. The deeper average frame size range of the Avigilon (~30KB to ~15KB) suggests that compression efficiencies can still be obtained by reducing the ratio of I-frames to P-frames (i.e., increase fps), and that the scene is not as complex as the nighttime scene.
The Axis curve (blue) is somewhat anomalous as its I- to P-frame ratio is a constant, and as such we would not expect its range to be as deep as experienced here in the intersection scenario. Indeed the Axis' range was ~5KB in the daytime and nighttime scenes versus the ~10KB range seen here (25KB to 15KB).
CBR Strategies for Bitrate vs. Frame-Rate Optimizations
Setting the right bitrate for a particular frame rate is significantly harder in CBR than in VBR. With VBR, the camera automatically adjusts the appropriate bit rate when you choose a different frame rate. By contrast, with CBR, the admin has to manually adjust the bit rate. For example, with a camera such as Sony, if the default bit rate is 2Mb/s, if you change the frame rate from the default of 30 to 15, the bit rate stays the same. What happens is that the camera will decrease the compression (or Quantization level) to decrease the amount of loss in the image. The key potential downside is that this can waste bandwidth. At a certain point, increasing quantization levels have little to no practical impact. That is, the mathematical loss decreases but the gains are imperceptible to the human eye. For background on this, please review our Bandwidth vs Image Quality report that digs into the issue of quantization.
When using CBR, if possible, try running in VBR mode first to get a baseline bandwidth level and use that as your CBR setting. Alternatively, export a few sample clips at different CBR bit rates, run this in a stream analyzer and pick the bit rate that results in a DRF of 32 or less. The final easy, low tech, alternative is to simply set different CBR bit rates, view the sample images and choose the lowest bandwidth image where you cannot spot any material differences in quality.
- Avigilon 1.0MP-HD-H264-B1 (MSRP $645) -720p D/N; 1/2.7" CMOS; F1.6; 0.4/0.04 Lux (Color/BW)
- Axis P1344 (online $759) - 720p D/N; 1/4" CMOS; F1.2 Computar ; 0.05 Lux (BW)
- Sony CH140 (online $800) - 720p D/N; 1/3" CMOS; F1.2 Fujinon; 0.1 Lux (BW)
Here are the firmware versions of each camera:
- Avigilon 1.0MP-HD-H264-B1 - fw 188.8.131.52(3445)
- Axis P1344 - fw 5.22.2
- Sony CH140 - fw 1.26.01
For VBR tests the two (2) cameras were left at their default VBR configurations. For each of the three key scenes (daytime indoor, nighttime indoor, and busy intersection), the cameras were recorded at different frame-rates (1, 5, 10, 15, and 30 fps). Average bit-rates and average frame sizes were obtained for analysis during each scenario.
5 reports cite this report:
Related Reports on Bandwidth
Most Recent Industry Reports
The world's leading video surveillance information source, IPVM provides the best reporting, testing and training for 10,000+ members globally. Dedicated to independent and objective information, we uniquely refuse any and all advertisements, sponsorship and consulting from manufacturers.