10-27-2008 03:59 PM
We have rolled out 512 WAEs on the edges and a couple of the 7326 on the core. The average bandwidthbetween an edge and the core sites is about 2 MB..We're only doing the CIFS files for now and getting a pretty good performance on them (80-90% compression). However, when looking at the data in more details, we noticed as good of a compression as we're getting on small/medium files, the optimization on the large files (30MB) is lagging far behind. Are there any tweaks we could make on these WAE's to improve the performance of the large files?
Thanks..
10-29-2008 03:18 AM
Greg,
Just in terms of compression, there aren't really any tweaks to apply for files of different sizes. What type of compression ratios are you seeing? Are the files opened/copied multiple times?
Zach
10-30-2008 08:47 AM
Zach,thnx for your response..One interesting trend we have noticed with respect to this issue is the first time the
file is being opened after it has been written, the latency is OK; - it's when the file is opened subsequent to this that the latency goes up precipitously. This works
completely opposite to what I have read about this product - the first time the file is opened, it gets pulled from the core to the edge and, therefore, is the longest poll in the tent. However, any subsequent times opening the file should show noticeable improvements in latency, which is NOT the case here..
11-03-2008 01:35 PM
Greg,
Is this the same issue you started a new thread on?
Zach
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide