Jeff,
>> In essence, what you're saying is that, at no point was Silver Peak delivering < 20% time reduction and at times, Silver Peak was able to deliver up to 90%
>>time reduction for both 1Mbps and 10Mbps links on a 14MB DWG file. Is that an accurate statement??
>
> Yes, that is what I am saying.
Great. In that case, could you post the result for the 1Mbps testing?
> The purpose of those tests were to demonstrate application response time across the WAN, which is the problem being expressed by AutoCAD end users.
> Data reduction numbers were not the focus, although we typically observe that those numbers are on par with the time reduction percentages. We don't do
> caching or any application-layer tweaks, so it is safe to say that these results are primarily due to our deduplication technology.
If the results are, like you say, primarily due to your deduplication technology, then the data reduction number is very relevant. Afterall, isn't deduplication the reduction of data? The data reduction number becomes even more important when you have low bandwidth links like 1Mbps.
And I quote from the Infoworld article:
"Riverbed is affected by the AutoCAD file format/ISP setting issue more so than rival Silver Peak, and Silver Peak would like the world to know. To be clear, Riverbed will still accelerate AutoCAD DWG files over the WAN, even on a full save, but the data reduction is less than what Silver Peak is able to accomplish. The AutoCAD file problem is a very specific use case and not an indicator of any larger technology issue with Riverbed. Silver Peak's data deduplication technology is able to handle this particular problem much more gracefully than Riverbedâ⠬⠢s."
So the question boils down to this: what is the data reduction number for Silver Peak for the 14MB file with ISP=0?
At the risk of sounding like a broken record, can you please post the numbers for the baseline and when you ran the test with ISP=0? This will enable everybody to understand the effectiveness of Silver Peak's deduplication technology and the effect it has with AutoCAD 2007/08. Once again, I want to re-iterate the fact that time reduction is not the same as data reduction. I'm not saying that time reduction and data reduction are not related because they certainly can be given the right circumstances. However, what I am saying is that it makes no sense to take the number for time reduction and then assume that same number for data reduction.
Case in point: When downloading files from a domain controller with SMB Signing turned on (enabled and required), Riverbed Steelheads, cannot perform latency optimization but it can perform data reduction. This means that it's entirely possible to have 90% data reduction rate and yet the time reduction may be close to 0%. Reason for the lack of time reduction? CIFS protocol chattiness. However, this chattiness has nothing to do with the Steelhead's ability to deduplicate the data.
The reverse is also true. Given a big pipe, it's entirely possible to see a 90% time reduction, and yet the data reduction rate may be close to 0%. In this case, deduplication is virtually ineffective but other optimizations kick in to reduce the time it takes to complete the operation(e.g. removing CIFS chattiness). Note that it's possible to have a negative data reduction rate (i.e. sending more data than without using the WDS appliance) and yet still experience time reduction.
As you can see, if you take the time reduction number and assume it's the same for data reduction (or vice-versa), you'd come to the wrong conclusion.
Also, I know that Silver Peak can optimize CIFS traffic as well. Wouldn't the CIFS optimization help with removing the chattiness of CIFS and make the save operation of AutoCAD quicker?
Best regards,
Blanco