Blue Coat SG210-25-M5 Leaflet
Bandwidth Management/Traffic Shaping
This technique assigns a priority to a particular type of
application. This priority has an effect both on the order
the traffic is sent in, and in the amount of guaranteed
bandwidth the application is allocated, regardless of
other traffic on the network. This technique ensures that
the network is available for the highest priority traffic.
Likewise, less important applications can be throttled
back and assigned limited bandwidth to help ease
network congestion.
the traffic is sent in, and in the amount of guaranteed
bandwidth the application is allocated, regardless of
other traffic on the network. This technique ensures that
the network is available for the highest priority traffic.
Likewise, less important applications can be throttled
back and assigned limited bandwidth to help ease
network congestion.
Protocol Optimization
Protocol optimization takes protocols that are inefficient
over the WAN (e.g., CIFS, MAPI, HTTP, TCP, HTTPS) and
makes them more efficient – typically by converting
a time-consuming serial communication process
into a more efficient parallel process where many
communication tasks are handled simultaneously. There
are a variety of other optimization techniques, depending
on the protocol (e.g., TCP session reuse). While protocol
optimization does not reduce the amount of bandwidth an
application consumes, it can greatly accelerate delivery of
applications and reduce latency in the process.
over the WAN (e.g., CIFS, MAPI, HTTP, TCP, HTTPS) and
makes them more efficient – typically by converting
a time-consuming serial communication process
into a more efficient parallel process where many
communication tasks are handled simultaneously. There
are a variety of other optimization techniques, depending
on the protocol (e.g., TCP session reuse). While protocol
optimization does not reduce the amount of bandwidth an
application consumes, it can greatly accelerate delivery of
applications and reduce latency in the process.
Byte Caching
Byte caching is as it sounds – caching of repetitive
patterns in the byte stream. Byte caching observes
repetitive patterns in application traffic, symbolizes those
patterns with a token, and sends the token in lieu of the
bulky traffic. These tokens are typically only a byte or
two, but symbolize blocks of data as large as 64KB. Byte
caching is typically not application-specific, and operates
at a lower level, optimizing all TCP traffic.
patterns in the byte stream. Byte caching observes
repetitive patterns in application traffic, symbolizes those
patterns with a token, and sends the token in lieu of the
bulky traffic. These tokens are typically only a byte or
two, but symbolize blocks of data as large as 64KB. Byte
caching is typically not application-specific, and operates
at a lower level, optimizing all TCP traffic.
Object Caching
Object caching is very different than byte caching – it is
protocol/application specific, and is an all-or-nothing
affair. If the cache contains the object, the user is
immediately served the object from a local store –
virtually eliminating latency and WAN bandwidth
consumption. If the cache does not contain the object (or
contains an outdated version of the object), then for that
particular transaction, a new object must be reloaded into
cache and the performance gains are realized the next
time the object is requested.
protocol/application specific, and is an all-or-nothing
affair. If the cache contains the object, the user is
immediately served the object from a local store –
virtually eliminating latency and WAN bandwidth
consumption. If the cache does not contain the object (or
contains an outdated version of the object), then for that
particular transaction, a new object must be reloaded into
cache and the performance gains are realized the next
time the object is requested.
Compression
Inline compression can reduce predictable patterns even
on the first pass, making it an ideal complement to byte
caching technology.
With MACH5, all of these techniques work together to
optimize application delivery to remote locations. For
example, if the object cache contains an outdated copy
of a document, the byte caching capability has patterns
and tokens that require only the tokens, plus the changes
to be sent. What little is sent is then compressed, and
protocol optimized (reducing bandwidth consumed and
latency/round trips). All of this is prioritized according
to the enterprise’s preferences, using bandwidth
management, such that the important applications get
through first with the bandwidth they need.
By combining these technologies into a single solution,
Blue Coat MACH5 gives organizations the complete toolkit
they need to optimize their entire WAN, covering more
application types with more technologies than any other
optimization solution.
on the first pass, making it an ideal complement to byte
caching technology.
With MACH5, all of these techniques work together to
optimize application delivery to remote locations. For
example, if the object cache contains an outdated copy
of a document, the byte caching capability has patterns
and tokens that require only the tokens, plus the changes
to be sent. What little is sent is then compressed, and
protocol optimized (reducing bandwidth consumed and
latency/round trips). All of this is prioritized according
to the enterprise’s preferences, using bandwidth
management, such that the important applications get
through first with the bandwidth they need.
By combining these technologies into a single solution,
Blue Coat MACH5 gives organizations the complete toolkit
they need to optimize their entire WAN, covering more
application types with more technologies than any other
optimization solution.
Copyright © 2007 Blue Coat Systems, Inc. All rights reserved worldwide. No part of this document may be reproduced by
any means nor translated to any electronic medium without the written consent of Blue Coat Systems, Inc. Specifications
are subject to change without notice. Information contained in this document is believed to be accurate and reliable,
any means nor translated to any electronic medium without the written consent of Blue Coat Systems, Inc. Specifications
are subject to change without notice. Information contained in this document is believed to be accurate and reliable,
Blue Coat Systems, Inc. 1.866.30.BCOAT // 408.220.2200
Direct
// 408.220.2250
Fax
// www.bluecoat.com
however, Blue Coat Systems, Inc. assumes no responsibility for its use, Blue Coat is a registered trademark
of Blue Coat Systems, Inc. in the U.S. and worldwide. All other trademarks mentioned in this document are
the property of their respective owners. v.SB-MACH5v5-1007
of Blue Coat Systems, Inc. in the U.S. and worldwide. All other trademarks mentioned in this document are
the property of their respective owners. v.SB-MACH5v5-1007
Solution Brief: MACH5 Acceleration Technology