Open Transfers by Folder
 

I am experiencing a situation where all of my upload links are being 'hogged' by users downloading 348MB(+!) files (I offer 4 of them), preventing users from accessing the other ~900 files (3.3MB the norm).

I would like to be able to have a Video folder with a limit of simultaneous accesses and a Music folder with a different limit of simultaneous accesses, for instance. That way, the long-winded Video uploads could still take place without preventing the Music uploads from happening.

I really only planned on hosting Music files; the Video files being accessed were intended to be strictly my downloads until the 'collection' was complete, then shared as a full set. But I found that users were D/Ling even while the transfers were incomplete. Consequently I could not exclude them when the transfers completed until the set was complete (as I had intended). Now there are 20 Video D/Ls going on, and (usually) 10 Video D/Ls queued by the users ... leaving no room for the smaller D/Ls to even get in!

I realize that this is fairly close to the "limit simultaneous accesses to a file" in the opening post in this thread. I hope the software design staff will consider this a refinement of that project item.

Edit: It is ironic that all of these D/Lers of 400+MB videos files are limitted to 3kbps transfer rates! The estimated duration of the D/Ls exceeds two days in most cases. So my intended target users cannot get in at all, because all of the possible accesses are taken up by slow systems working on huge files. :mad:

Just another vote for your idea.

Could at least PFS bandwidth/slots (the sharing of incomplete file chunks) be halved to give room for other uploads with fewer alternate locations?

I wonder if allocating dynamic bandwidth "pipes" to folders might be a way to help the large/small file problem. Shared folders could be dragged in the Library up or down a priority queue, a bit like the one used in the downloads panel.

Folder class A-- 60% pipe of available upload bandwith. When unused, the bw fattens the pipes of the other classes

Class B--30% pipe

Class C (incomplete)--10% pipe

sigh. Wish I learned to code ;)