Upload Filesize 98Kb even though File is not!

[atombomb]

Hello,
I am a registered user (well, at least until the *next* upgrade requires another payment!)

When I check the Monitor Tab, it shows the things people are\have uploaded. Quite a few of them are showing as files of 98Kb in size which they are not.

Is this a Limewire bug - I understand uploads are chopped into 97.7Kb 'packets' ?

I know it's not working properly for the end user 'uploader', because if I watch someone upload when it is showing 98Kb, it zooms across the "Progress" box in about 2 seconds.

Any ideas ? The files are not 98Kb and I can play\view them perfectly locally ??

Regards,
Paul

[trap_jaw]

It's not a bug, it's a feature and it works very well. I've been downloading in 97.7k chunks for almost a month know (since it was released in the cvs version) and it works just fine. There are now some problems with the upload view, however.

[atombomb]

Hi Trap-Jaw,
Feature ? ;-D

The problem is, I can see people trying to upload, but the progress zooms across the screen and it finishes.

I just took another look, and I can see it initially displays the correct size for about 1 second, and then flips over to a size of "98Kb" and the person @ the other end doesn't get all of the file.

What should I do ?

Cheers.

[sberlin]

like trap_jaw said -- it's a feature. people now upload/download multiple chunks of the file, in approx 98k pieces. this helps swarming, so you can download from lots of hosts at the same time. you'll naturally get more data from the ones that are quicker. you aren't disconnecting & reconnecting after each 98k piece, so it's nothing to worry about.

[atombomb]

Ah! Goddit, thanks. I understand now! [blushes in stupidity]

So it's the same as when my client is downloading from Multiple hosts. Cheers All.

[salemgman]

Good lord! I saw this also, but thought it was just a flaw.

Why do you have such insanely small chunks? If I EVER did such a crazy thing when posting binaries to newsgroups, I'd get flamed day and night for about a month!

Doesn't 98KB chunks create more traffic by having a lot more upload requests? Worse, in a situtation where the upload host is saturated, latency will cause a net slowdown in the transfer...

A more common posting size (on binary newsgroups) is a meg or two. That'd be about 20 times fewer start requests.

Here is what I would actually recommend... Make the chunk size a minimum of some number (98KB is fine), but make the default size 5% of the file size (1/20th). This way, if you're downloading a 3MB mp3 file, you'll be doing 150KB chunks, but if you're doing a 650MB iso image file, you'll be doing 32MB chunks.

Remember, there are still modem users out there, and at a whopping 3-5KB/sec, excess start requests of 128 bytes each add up!

[bink]

Yikes, is that what that is? I thought someone was stuck in a loop, or worse, maliciously downloading the same small file over and over.

Is this in the FAQ?

[Nascaracsan]

Ok let me see if I got this 98k file size thing right.....If the file being uploaded is 15mb...but upload screen says 98k,.the uploader is getting uploads from more than one person. is this right.

If the file size says the correct size, 15mb, then the uploader is only getting the file from you. ?

What if the file size says 327 or other incorrect file sizes?

If you have the "clear completed uploads" checked, well these 98k files be deemed as completed and cleared at the end of each one? Or will they keep looping until completed?


Nas