Steelhead Appliance

[sharonk868]

---

bgilbert wrote:

That's a tough question.  The MAPI optimization has 3 components.  The first is data deduplication, which will eliminate all data redundancy from the Outlook client(s) to the Exchange server.  This optimization's key value is the ability to reduce the impact that Exchange, especially cached mode, has one the WAN.  Think 50 users in a branch pulling down the same corporate presentation and flooding the WAN.  With data streamlining, the bytes that constitute the presentation are only pulled down once.  This is mostly not a latency problem.

The next two optimizations address latency at the TCP layer as well as at the MAPI protocol layer.  There is no minimal RTT latency required for this optimization to work, but its effectiveness is determined by the response time impact you are experiencing as a result of having a high latency connection between your Outlook clients and Exchange server.  Many Exchange operations start getting slow starting at 20 to 30ms RTT and the problem gets really bad when you go above 30ms RTT.  The latency impact will vary based on your working set and the type of operations you are performing.

---

Thanks you for the post.
Hi guys, Im a newbie. Nice to join this forum.
__________________
http://watchmoviesfree.biz

[bgilbert]

That's a tough question.  The MAPI optimization has 3 components.  The first is data deduplication, which will eliminate all data redundancy from the Outlook client(s) to the Exchange server.  This optimization's key value is the ability to reduce the impact that Exchange, especially cached mode, has one the WAN.  Think 50 users in a branch pulling down the same corporate presentation and flooding the WAN.  With data streamlining, the bytes that constitute the presentation are only pulled down once.  This is mostly not a latency problem.

The next two optimizations address latency at the TCP layer as well as at the MAPI protocol layer.  There is no minimal RTT latency required for this optimization to work, but its effectiveness is determined by the response time impact you are experiencing as a result of having a high latency connection between your Outlook clients and Exchange server.  Many Exchange operations start getting slow starting at 20 to 30ms RTT and the problem gets really bad when you go above 30ms RTT.  The latency impact will vary based on your working set and the type of operations you are performing.

[raghvendrais31]

At which Latency Riverbed appliance should be used for MAPI traffic optimization?

[bgilbert]

Hi Dereck,

When an Outllook 2003 client talks to an Exchange 2007 server, their is no encryption by default and the protocol negotiated is MAPI 2K3. Steelheads can then work their magic.

If the client is Outlook 2007 and the server is Exchange 2003, encryption must be disabled on the client in order for Steelheads to optimize.

QUOTE(Dereck Johns @ Aug 29 2007, 09:44 PM) 484

Bob,

Thanks this is most helpful. Is it safe to assume the behaviour using an Outlook 2003 client to an Exchange 2007 server is similar to the above extract from your original response?

[Dereck]

QUOTE(Bob Gilbert @ Aug 23 2007, 10:08 PM) 471

The first configuration is when Outlook 2007 clients talk to Outlook 2000/2003 servers, the MAPI 2000/2003 protocol is negotiated. Riverbed provides native data streamlining (data reduction) and application streamlining (layer-7 acceleration) for these mixed mode environments because the older protocol is effectively negotiated by the application. There is nothing you need to do here.


Bob

Bob,

Thanks this is most helpful. Is it safe to assume the behaviour using an Outlook 2003 client to an Exchange 2007 server is similar to the above extract from your original response?

[ianhoyle]

- disregard this post -

[bgilbert]

Hi Dereck,

Exchange 2007 performance should be similar to Exchange 2000/2003. It is important to understand the following three configurations and their impact on Steelhead's ability to optimize/accelerate.

The first configuration is when Outlook 2007 clients talk to Outlook 2000/2003 servers, the MAPI 2000/2003 protocol is negotiated. Riverbed provides native data streamlining (data reduction) and application streamlining (layer-7 acceleration) for these mixed mode environments because the older protocol is effectively negotiated by the application. There is nothing you need to do here.

The second configuration to note is when Exchange 2007 and Outlook 2007 are used together, a new context of the MAPI protocol is used. Riverbed RiOS software 3.08 and greater or 4.02 and greater is required to get optimization. These RiOS software releases support a protocol negotiate feature that will allow the new protocol context to be negotiated down to the MAPI 2003 context so Riverbed's layer-7 acceleration can take place.

The third configutaion is the fact that in contrast to Outlook 2000/2003, Outlook 2007 uses encrypted communications with Exchange server by default. Leaving encryption on will disable Riverbed's MAPI optimizations. You must turn Outlook 2007 encryption off even if the Exchange server is older than 2K7.

Thanks,

Bob

[Dereck]

Do we have any Exchange 2007 data available?

[bgilbert]

Attached is Riverbed's performance brief covering Microsoft Exchange. The test summary is:

- More than 54 times faster email transmissions to multiple recipients in a branch
- More than 10 times faster transmission for a sender and recipient in the same branch
- Up to 97% reduction in bandwidth utilization

Does anyone have any Microsoft Exchange performance results or any feedback to share?

Message Edited by bgilbert on 01-28-2009 04:44 PM