Only Remote-Desktop and Replication with 0.0 Reduction

Question

Hi guys,
I have a solution with 16 WAAS 4.4.3 and I got good numbers in all default applications except Remote-Desktop and Replication
( All Traffic 53% of Reduction).
I can understand not otimize Remote-Desktop Applications cause the customer is using Metaframe with crypto and already compacted and
using too RDP with crypto/compacted.
But in the Replication I would expect some gain in Active Directory and MS-FRS Replication.
I got 0.0, Actually, the optmized traffic is biggest that the Original Traffic.
I have to modify something in the Microsoft servers to be able to got reduction in Replication Application ??
I'm using all the Default Classifiers in Replication Application
Double-Take                            LZ+TFO+DRE       1100, 1105
EMC-Celerra-Replicator            LZ+TFO+DRE       8888
MS-AD-Replication1                 LZ+TFO+DRE       UUID:e3514235-4b06-11d1-ab04-00c04fc2dcd2
ms-content-repl-srv                   TFO                     507, 560
MS-FRS1                                LZ+TFO+DRE       UUID:f5cc59b4-4264-101a-8c59-08002b2f8426
netapp-snapmirror                    LZ+TFO+DRE       10565-10569
pcsync-http                             LZ+TFO+DRE       8444
pcsync-https                           TFO                      8443
rrac                                        TFO                      5678
Rsync                                     LZ+TFO+DRE       873
Thanks a Lot
My Best Regards,
Andre Lomonaco

Answer 1

As you said, you need to only send the changes over the line.
Java can not tell you what has changed, so you need to either write some JNI, or do a check on the current image, with the last image. (this would eat quite a bit of CPU time on the server).
It might be worth looking at the source for VNC, and other simler products.
The simpliest solution would be to split the image into blocks of x by y pixels, then do a pixel-by-pixel check on that block, and only send the block if it has changed.
Next thing to think about is scrapping RMI, and using raw sockets. RMI has a fair sized overhead.
Zipping a JPEG is unlikely to have any effect. A JPEG is already compressed.
You might want to look at a lossless compression format, like PNG, as the JPEG will have articles. This might be acceptable. If so, changing the compression ratio of the JPEG might be an option.
Finally, the bottle neck might be the call to Robot.createScreenCapture. This is not the fastest method.