speed display

[usurper]

The new beta is uploading locally much faster, from 500 to 900 K/s on my lan, but the speed doesn't display right. Glftpd (uploading to it locally) shows 900K/s, and I know the math there is correct =), and the progress bar in flashfxp shows 900K/s too, almost exactly the same as glftpd, but when the file is done, the summary line shows only 700K/s:
Transferred: xxxxxxxx.zip 2,914,692 bytes in 4.93 (723.35 KB/Sec)

[Fusion]

~700 seems right. No transfer has max-speed on the first byte transferred, the average # simply reflects that.

[bigstar]

It appears the speed is effected by delays in the transfer complete message (scripts like zip checking)

[Shark]

Hi Usurper, if your the real one :)

[usurper]

bigstar: you're right, it was zipscript - oops

i didn't think such a short delay would result in such a big average speed difference.

[bigstar]

rather than waiting for the "226 " decided to change it to stop the elasped timer on the first line of the reply "226-", so far that doesn't seem to cause any problems.

[Ethanol]

Originally posted by usurper

Transferred: xxxxxxxx.zip 2,914,692 bytes in 4.93 (723.35 KB/Sec)
I'm sorry, but I work this out to be 577.36 KB/Sec using the above two figures, and not 723. Even if there were delays imposed, the result should still be calculated from the two values presented (time and bytes)

[usurper]

hmm, good point.
I
can't believe that short delay would cause the speed to get as far down as 577K/s though, it's gotta be something wrong with that time displayed. Maybe it counts from the time it issues the STOR command, instead of the time it sends the first byte of the file? But on my lan the latency is almost null, so that still should only make a minor difference.

[bigstar]

I've done some tests and each time I get the correct results.

I can't explain why your results differ

KB/S = filesize / 1024 / elapsedtime

The elapsed time doesn't start until it starts sending data.