I use riverbed steelhead appliances on a few links ranging from 40ms to 240ms.
I tend to get about 85% savings on actual traffic that goes through.  I think 
what is very important to know is the type of traffic you expect to optimize.  
Riverbed is -very- good at MAPI and CIFS traffic, which is the majority of what 
we want to improve.  With the right caching settings and enough disk space you 
can simply avoid dumping traffic to expensive WAN links and serve it locally, 
instead.

For standard tcp based apps, it does a great job with window sizing and 
predictive acknowledgements.
There have been a few applications that we have trouble with the steelheads - 
particularly VOIP and Video, but these are easy enough to exclude from in-path 
rules.

It is night and day with and without riverbed.  I don't have experience with 
the Cisco WAAS product.

-JP


-----Original Message-----
From: cisco-nsp-boun...@puck.nether.net 
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Saxon Jones
Sent: 09 August 2012 9:38 AM
To: harbor235
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Riverbed

I only have experience with Cisco WAAS but if you're on anything with decent 
latency (<10ms) they caused more (performance) problems for us than they 
solved. For us the incremental cost of upgrading our bandwidth in most 
locations was low enough that we didn't take WAAS out of the pilot (and we 
preferred local services to WAAS where we have poor connections, due mostly to 
the perceived reliability of those connections). This information is a few 
years old, though.

-saxon

On 9 August 2012 09:03, harbor235 <harbor...@gmail.com> wrote:

> Can anyone share the experiences with Riverbed products, does the 
> optimization results justify the cost? Are there protocols that do not 
> work well with the optimization process? With Cisco devices?
>
> I realize this is the the correct forum, but most people in this forum 
> that require WAN optimization would also be in this forum.
>
>
> thank you
>
>
> Mike
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp@puck.nether.net 
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
_______________________________________________
cisco-nsp mailing list  cisco-nsp@puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
The contents of this message may contain confidential and/or privileged
subject matter. If this message has been received in error, please contact
the sender and delete all copies. Like other forms of communication,
e-mail communications may be vulnerable to interception by unauthorized
parties. If you do not wish us to communicate with you by e-mail, please
notify us at your earliest convenience. In the absence of such
notification, your consent is assumed. Should you choose to allow us to
communicate by e-mail, we will not take any additional security measures
(such as encryption) unless specifically requested.


_______________________________________________
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to