About Bandwidth Throttling

You can limit the speed for uploading and downloading data to the appliance in a process known as bandwidth throttling.

You can use bandwidth throttling, for example, to avoid a situation where the network performance you need for completing a particular task is impacted by other users who are uploading objects to the web or are requesting large downloads from the web.

Two methods of bandwidth throttling are available on Web Gateway.

• Basic bandwidth throttling — Using this method you can limit the speed of data transfer from a client to a Web Gateway appliance and from the appliance to a web server.
  
  Under this method, you configure suitable rules that specify a maximum transferring speed. When an upload or download request matches the criteria of a rule, the speed of transferring data for this request is limited as specified in the rule.
   
• Bandwidth throttling using classes — Using this method you can limit the speed of data transfer from a client to a Web Gateway appliance and from the appliance back to the client, as well as from an appliance to a web server and from the web server back to the appliance.
  
  Under this method, you configure classes of transferring speed and suitable rules that make use of them. A class is specified by a speed range, for example, 1001 to 2000 Kbps.
  
  When an upload or download request matches the criteria of a rule, the speed of transferring data for this request is limited as specified by the class used in the rule. This speed must not exceed the maximum value, nor fall below the minimum.
  
  You can, for example, create a rule that applies to downloads of Windows updates and prevents them from consuming all of the bandwidth that is available on your system by limiting it to the transferring speed range of a particular class.
  
  You can also limit the speed of data transfer performed for traffic that does not use the proxy functions of
  
  Web Gateway, which means that the rules of your web security policy are not applicable.
  
  This traffic originates, for example, when Web Gateway log files are uploaded to an external server or data is downloaded from an external server to update information required for performing filtering functions on Web Gateway.