Re: compressed protocol

Michael Fuhr wrote:

> On Fri, Sep 15, 2006 at 06:34:48PM +0200, zeljko wrote:
>> I'm testing over DSL line (test server have 256k Upload and 1MB
>> download). Results are based on this connection.
>> Server : PIV 3Ghz HT, 1GB RAM. (DSL D 1MB U 256k)
>> Client : PIV 3Ghz HT, 1GB RAM. (DSL D 3MB U 384k).
>>
>> nTier results shows real compression (faster more than twice).
>
> What does a sniffer like tcpdump or wireshark/ethereal show? Let's
> see how much data is being sent over a compressed vs. uncompressed
> connection and how long the data transfers are taking.
>

I've tried sniffing with ethereal , but there's too much data, this is what
ssh with -v command parameter says. (amount of incoming data and
compression factor). It shows minor compression with query data.

ls -al /usr/lib
This is ssh log (compression enabled):
debug1: compress incoming: raw data 135639, compressed 20931, factor 0.15

Same query as in my previous posts.

This is ssh log (compression enabled):
debug1: compress incoming: raw data 682162, compressed 680894, factor 1.00

Query which returns integer field only:
debug1: compress incoming: raw data 193514, compressed 192030, factor 0.99

Query which returns varchar(3) only:
debug1: compress incoming: raw data 178999, compressed 177505, factor 0.99