Alternate downloads groups (ADGs)
Posted: November 23rd, 2013, 7:02 am
*Feature description*
"alternate download group" (ADG), allows the user to group two or more items together and declare them as "alternate downloads". Items that are part of an ADG are downloaded sequentially (one after another). If one item of the group gets downloaded successfully, all other items are automatically discarded by sabnzbd.
*objective*
I recently discovered that some people who are connecting to cheap servers or interested in old/aging items often end up downloading "all possible items" for a single media because they anticipate that several downloads would fail. To make sure that at least one succeeds, they insert all possible nzbs in sabnzbd. Consequently, even when one of the downloads succeeds, sabnzbd keeps downloading the subsequent items.
If many people are doing this, this might be the source of very high bandwidth usage on servers due to people who are downloading files that they don't need.
*interface proposition*
While the download of pieces is already parallelized by the number of server connections, Sabnzbd downloads files in sequence. Which means there is an implicit "default alternate download group" composed of all the items in the queue.
The interface would somehow allow users to move a download item to either an already existing ADG or to create a new ADG.
Please don't hesitate asking if you want more information on how I see this feature.
regards,
"alternate download group" (ADG), allows the user to group two or more items together and declare them as "alternate downloads". Items that are part of an ADG are downloaded sequentially (one after another). If one item of the group gets downloaded successfully, all other items are automatically discarded by sabnzbd.
*objective*
I recently discovered that some people who are connecting to cheap servers or interested in old/aging items often end up downloading "all possible items" for a single media because they anticipate that several downloads would fail. To make sure that at least one succeeds, they insert all possible nzbs in sabnzbd. Consequently, even when one of the downloads succeeds, sabnzbd keeps downloading the subsequent items.
If many people are doing this, this might be the source of very high bandwidth usage on servers due to people who are downloading files that they don't need.
*interface proposition*
While the download of pieces is already parallelized by the number of server connections, Sabnzbd downloads files in sequence. Which means there is an implicit "default alternate download group" composed of all the items in the queue.
The interface would somehow allow users to move a download item to either an already existing ADG or to create a new ADG.
Please don't hesitate asking if you want more information on how I see this feature.
regards,