So, I thought I'd finally knock off adding compression to the DataPortal tonight. I started looking around for some guidance and found a few interesting threads, mainly this one: http://forums.lhotka.net/forums/t/7849.aspx?PageIndex=1
The conclusion of that seemed to be that binary WCF with NO zip compression is probably the best configuration. Did I interpret that right, and is that still the thinking?
I didn't made any throughtput tests for WCF but I did a lot for remoting with several algorithms. The general rule is:
"compression increases overhead - both in the sender and receiver side".
I can put it on a different way. For a 100M bit/second medium (network) I didn't find any compression algorithm that delivers data faster than using uncompressed data. If you haver serious load problems on your network or if you are using a slow medum (say a VPN to a remote location) you might get faster delivery of data because there is less data to transfer.
Hope that helps...
Thanks. That seemed to be the conclusion of the testing in the thread I referenced in the original post above.
I just wanted to confirm my understanding of that as the current best practice / recommendation with CSLA.
From my perspective, the recommendation is to do what works. That might sound trite, but it isn't. Different apps have different requirements, and you should do what works for your app.
My overall personal philosophy is also to use the least technology possible in any given case. So if you don't need to use compression to make your app work, then you shouldn't use compression. If you do need it, then you should use it.
With binary XML, compression seems to offer pretty limited benefit, but it does still have some benefit. It also causes overhead, so whether it provides value will depend on your specific scenario.
Copyright (c) Marimer LLC