0000540: Little enhanced sources dropping

(0001526)
hphde (reporter)
2005-12-01 10:33

A developers comment would be fine ...

(0001528)
Kry (manager)
2005-12-02 02:55

*yawn* I don't even find sources dropping useful at all, so I'm not much concerned about it.

How's that for a developer comment?

(0001529)
Xaignar (manager)
2005-12-02 02:58

Ignore Kry. ;)
Personally, I'd rather change swapping/dropping to happen transparently, so that there is no need for the user to fiddle with settings. I'll look at it once 2.1.0 is out.

(0001530)
Kry (manager)
2005-12-02 03:01

I'd rather have no dropping at all. it's stupid and pointless. Sources always come back, so it only wastes bandwith.

The only useful dropping is sending a NNP source to an A4AF where it might be more useful. That's all.

(0001531)
Xaignar (manager)
2005-12-02 03:03

The DeadSourcesList helps prevents sources from comming back before they have any chances getting needed parts. But in any case, I'll agree that source-swapping is more important.

(0001534)
hphde (reporter)
2005-12-02 15:49

Mh, okay, maybe telling this sources dropping was not so brilliant.
I was talking about the menue point "Sources Dropping" that allows more then just dropping but also sending sources (which makes sense) to other files etc.

Eg. you have a file with maybe 5000 people distributing it. Your hard limit is set to 600 you would get 600 sources and that's it. So if it would drop (send to other) sources it would have the chance to crawl the other more promising sources (not full, not queue rating >n) instead of just waiting for the 600 it first found. So far "sources sending" makes sense IMHO.

So if you activate that feature you will have a problem with all files that have sources less then "hard limit" because it's actually not a wide spread file. So we are back to my request ...
a) exclude files from dropping with sources < n (where n is maybe = "hard limit" and this is really easy to implement, maybe I should check the source with my rusty old C skills ;-) )
b) tag files to be excluded from sources dropping/sending (optional)

Thanks for the discussion anyway.

(0001542)
hphde (reporter)
2005-12-03 09:14

Slept a night over it. Maybe you should call the menu entry "Sources Handling" instead of "Sources Dropping". That would more closely reflect what it's supposed to be.

Issue History
Date Modified	Username	Field	Change
2005-08-17 17:44	hphde	New Issue
2005-12-01 10:33	hphde	Note Added: 0001526
2005-12-02 02:55	Kry	Note Added: 0001528
2005-12-02 02:58	Xaignar	Status	new => assigned
2005-12-02 02:58	Xaignar	Assigned To	=> Xaignar
2005-12-02 02:58	Xaignar	Note Added: 0001529
2005-12-02 03:01	Kry	Note Added: 0001530
2005-12-02 03:03	Xaignar	Note Added: 0001531
2005-12-02 15:49	hphde	Note Added: 0001534
2005-12-03 09:14	hphde	Note Added: 0001542
2008-07-14 15:10	Wuischke	Status	assigned => closed

Notes
(0001526) hphde (reporter) 2005-12-01 10:33	A developers comment would be fine ...

(0001528) Kry (manager) 2005-12-02 02:55	yawn I don't even find sources dropping useful at all, so I'm not much concerned about it. How's that for a developer comment?

(0001529) Xaignar (manager) 2005-12-02 02:58	Ignore Kry. ;) Personally, I'd rather change swapping/dropping to happen transparently, so that there is no need for the user to fiddle with settings. I'll look at it once 2.1.0 is out.

(0001530) Kry (manager) 2005-12-02 03:01	I'd rather have no dropping at all. it's stupid and pointless. Sources always come back, so it only wastes bandwith. The only useful dropping is sending a NNP source to an A4AF where it might be more useful. That's all.

(0001531) Xaignar (manager) 2005-12-02 03:03	The DeadSourcesList helps prevents sources from comming back before they have any chances getting needed parts. But in any case, I'll agree that source-swapping is more important.

(0001534) hphde (reporter) 2005-12-02 15:49	Mh, okay, maybe telling this sources dropping was not so brilliant. I was talking about the menue point "Sources Dropping" that allows more then just dropping but also sending sources (which makes sense) to other files etc. Eg. you have a file with maybe 5000 people distributing it. Your hard limit is set to 600 you would get 600 sources and that's it. So if it would drop (send to other) sources it would have the chance to crawl the other more promising sources (not full, not queue rating >n) instead of just waiting for the 600 it first found. So far "sources sending" makes sense IMHO. So if you activate that feature you will have a problem with all files that have sources less then "hard limit" because it's actually not a wide spread file. So we are back to my request ... a) exclude files from dropping with sources < n (where n is maybe = "hard limit" and this is really easy to implement, maybe I should check the source with my rusty old C skills ;-) ) b) tag files to be excluded from sources dropping/sending (optional) Thanks for the discussion anyway.

(0001542) hphde (reporter) 2005-12-03 09:14	Slept a night over it. Maybe you should call the menu entry "Sources Handling" instead of "Sources Dropping". That would more closely reflect what it's supposed to be.

Relationships