Poor performance when saving documents to remote share

dmann · ‎06-03-2008

The following operations appear to be optimized by WAAS while on servers behind the datacenter core WAE:

1. Navigating through directories

2. Opening files

3. FTP

4. HTTP

5. Copying files from the server to the workstation and vice versa.

However, when saving the files it takes a long time since it writes the entire temp file to the share and this does not appear to be optimized.

In this scenario the datacenter core is using a WAE 612 while the branch office edge is using a WAE 502 mod. Both locations are configured to use WCCP redirection.

Has anyone experienced something similar?

dstolt · ‎06-03-2008

David,

Have you double checked your connectivity directives to ensure they correctly reflect the WAN link parameters? What is the speed and latency for your WAN link?

Each type of MS Office program reacts to temp files differently, however they all should be able to take advantage of CIFS + L4 optimizations.

Dan

dmann · ‎06-06-2008

Yes. The office has an E1 and the delay is 140 ms. This is configured in the connectivity directive.

dstolt · ‎06-06-2008

Out of curiosity, what is your hardware (edge and core) and the memory in the boxes?

Do you see the connection in "sh tfo con sum" or is it inside the 4050 tunnel? If it's inside the tunel, it's being optimized, just taking way longer then a simple copy which uses different CIFS commands. Is it worse without WAAS?

Dan

dmann · ‎06-10-2008

612 with 2 GB in the core and 502 NME's at the branch offices.

dmann · ‎06-10-2008

The sh tfo con sum does show the connections as optimized. It is worse when optimization is turned off.

dstolt · ‎06-10-2008

Is the connection inside the tunnel or do you see a 139/445 connection for that client/server outside the tunnel?

You should see the connection under "sh cifs connection list"

Dan

dmann · ‎06-10-2008

I see the connections under the sh cifs sessions list as accelerated sessions.

dstolt · ‎06-10-2008

The only other think that I would have you check is your interfaces speeds and duplexs, however if your other application optmization are OK, you may not be able to do much more for the save operation which is contrained mostly by latency (reading from the temp file and completely replacing the original file).

Dan