Bandwidth management

From SpinetiX Support Wiki

Jump to: navigation, search

Effective management of bandwidth is important when integrating HMPs into an existing network of any size. Bandwidth management is not performed by network devices like the HMP, but by switches and routers designed for the purpose - in particular, technologies based around Quality of Service ("QoS") will be relevant to any installation. Some small-office/home-office routers employ their own methods of traffic prioritization as well - it is not always necessary to use enterprise-class equipment.

Note Notes:

  • Your HMP will efficiently cache content to conserve bandwidth. For more details, see full article on Caching.
  • If employing streaming on a network with multiple HMPs, consider delivering the stream via multicast instead of unicast. Multicast, if supported by the rest of the network infrastructure, significantly reduces the bandwidth required to deliver multiple concurrent streams. It also uses UDP which is better suited to streaming content than TCP.
  • It is relatively straightforward to plan for network capacity in regard to streaming content, as the bandwidth can be somewhat fixed. However, note that the network must consistently support the aggregate of all the data required. A 100mbps network running 10 x 5mbps streams will work only if other services do not use the bandwidth.
  • If using Client/Server mode or Pull mode, the bandwidth is harder to estimate because these services use TCP, and native congestion-control of TCP is aggressive and will attempt to use all available bandwidth. Most other services present on the network will also consume bandwidth in the same manner including VOIP, SAP, File and print services and other common corporate services.
  • Ideally, put bandwidth-intensive services on separate logical or physical networks, or employ traffic-shaping technology to prioritize them efficiently.
This page was last modified on 2 December 2016, at 12:36.