|
|
Post by Sparhawkpp on Mar 5, 2003 13:04:39 GMT -5
Im trying the new 2.5 version and see that the speed and uploaded/downloaded bytes calculations are bugged. I resetted the stats and downloaded a file and it said the top download speed was 384.41kb/Sec and that i downloaded 20.84Mb. It was a 15Mb file and the speed was max around 260kb/sec, the link speed is max 300kb/sec.
|
|
|
|
Post by Test User on Mar 6, 2003 13:33:17 GMT -5
Did you download a file from the WWW via http (in your web browser), via FTP, or use a NNTP newsreader to get the 15MB file from USENET? In the latter case, you can expect far more (2-40%) bytes to be transferred because USENET (newsgroups) don't directly support binary data and a file has to be encoded. Most modern newsreaders do this invisibly, but your system utilities (and NetPeeker) would reflect the true larger amount transferred even if your newsreader gave you the "effective/actual binary rates". yEnc is a new encoding standard that is much more efficient (+2% or so) than MIME or UUEncode which is the most common, but also causes binary files to "grow" 40% when tranferred.
If your "test" was via FTP or http transfer, then I have no idea why NetPeeker showed larger transfers than what you did. Both of those transfer protocals do handle binary files so there is no need for encoding expansion.
|
|
|
|
Post by Sparhawkpp on Mar 6, 2003 16:12:45 GMT -5
I downloaded the file from an ftp server with nothing else running, so the stats are only from that and they aren't correct. I have uninstalled netpeeker since it has given me bsod's.
|
|
