Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Kry]

...and please lfroen stop BOFHing

[lfroen]

stop BOFHing

BOFHing -?   ?(  ?(

[Kry]

trying to act like a BOFH

You know, we talked about that

[phoenix]

http://bofh.ntk.net/Bastard.html

[lionel77]

Originally posted by lfroen
lionel77:

avoid wasting upload bandwidth

What does it have to do with upload ?! By pausing file in download queue how exactly you save upload bandwidth ?

if you hadn't stopped reading my posting right there you would have understood:

lionel77 wrote:
the even bigger issue here is to avoid wasting upload bandwidth of the clients we would be downloading from.

same issue is missing here:

Originally posted by phoenix
What harm does this file causes beeing on the download queue?
1) Disk space allocation
2) Source exchange bandwidth

3) Binding upload bandwidth of the clients who are uploading chunks of the dead file to us

the whole idea is that downloading chunks of dead files wastes global upload bandwidth, assuming other clients are not exclusively sharing dead files. every time you download 400mb of a dead 600mb file you have wasted 400mb of precious upload bandwidth (of other clients) that could have been used for spreading complete files.


i do see phoenix point though, that we don't want to declare a file dead that is rare but still complete and to thereby reduce it's spread even further.
you are probably right, that the servers would be much better suited for such a monitoring task, so maybe somebody should bring that idea to lugdunum's attention...

[GonoszTopi]

My idea is: we already have "Last Seen Complete" value on PartFiles. It would be very easy to add a new switch to Preferences->Files saying >>Don't start "Never Seen Complete" files<<. Implementation wouldn't be much harder, too.

(Just a suggestion, in case we decide to implement it sometimes)

[Kry]

I agree.

[phoenix]

lionel77,

I think you understood what I wrote, but you still assume that a file is dead when you say:

3) Binding upload bandwidth of the clients who are uploading chunks of the dead file to us

I think GonoszTopi suggestion is a good compromise for a "client side dead file recognition".

Cheers!

[lionel77]

@phoenix
yep, that was meant under the assumption that the file really is dead.


implementation via the existing variable 'last seen complete' should be pretty straight-forward but i'm still undecided about the risk/benefit ratio:
we've listed most of the advantages of such a feature above.
the possible risks that i see are:
- when releasers are using chunk-hiding mods, our download would not start before every chunk has been uploaded by the releaser at least once. so our download would be slowed down in these situations. no big deal for me but other people are more impatient. in the extreme case of everyone using the described delyed download feature, releases would be impossible with such a hide-chunk mod, but again this is to unrealistic to be a real problem
- if a file is barely complete on the network and its chunks are distributed very sparsely we could fail to detect that the file is actually complete and therefore never start to download it. this would actually be pretty bad but i personally can't estimate what the likelihood of this happening would be. would this be affected by restarting amule? (i.e. does amule save info on seen chunks of a file or not?)

[superstoned]

I'd say this is a great idea.

we should think of a way to ensure not-complete files don't spread. maybe a newly added file would only start at low priority, and only increase when it is seen fully available. And don't share such files. And probably warn the user after say 7x24 hours online and say the file seems to be unavailable, and further waiting is quite pointless (remove file now [ ] do this automatically from now).

but there should be a way to ensure uncommon and new files DO get shared. Maybe first we should share and download the file, but if after one hour the file does not seem to be complete, stop sharing and downloading...