Finally managed to get it. The figure shown by kpppload is (Kilo)
*bytes* per second and not *bits* per second. Search on google had not
revealed much so I was almost on the verge of downloading the code and
peering at it.
But a better idea saved the day. I used ping to use a specific number
of bytes ( -s and -c options) with kpppload running. This confirmed that
the unit is indeed *bytes*.
This made me a lot happier ;) Moreover now one can say that compression
does work for about an year before i used to see that the speed used peak
to some 12/16 k bytes/sec ( for an instant only ). Since I use a 56kpbs
modem the max that one can possibly obtain is 7K. So definetely some
compression was taking place either at
i) ppp software level
ii) hardware compression by modem
or
iii) the web server was sending compressed streams
-- sreangsu
On Tue, 20 Feb 2001, sreangsu acharyya wrote:
> can anyone tell for sure what is the unit used by kpppload. It says K/s
> but is it kilo *bits* per sec or kilo *bytes*. Evidence gathered so far is
> pretty confusing.
>
> 1) the speeds in netscape and kpppload differs by a great extent but
> lesser than 8 times.
>
> 2) I have a 56kpbs modem so the max that i can get is 7 Kilo bytes per
> sec, but I do remember kpppload showing some 12K/s ( Ok just for a
> second...and it was ages ago ). So it can be either that the speed shown
> by kpppload was 12 k bits per sec, or that the 12Kbytes per sec was after
> decompression. ( So this opens another question, does kpppload give the
> speed before or after the compression )
>
> 3) While ftp ing something with hash # the rates shown by kpppload and ftp
> do seem to match in which case it is k bytes per second.
----------------------------------------------
LIH is all for free speech. But it was created
for a purpose. Violations of the rules of
this list will result in stern action.
