Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to Prefer Newer Usenet Releases #6057

Open
1 task done
PCJones opened this issue Sep 30, 2023 · 4 comments
Open
1 task done

Ability to Prefer Newer Usenet Releases #6057

PCJones opened this issue Sep 30, 2023 · 4 comments

Comments

@PCJones
Copy link

PCJones commented Sep 30, 2023

Is there an existing issue for this?

  • I have searched the existing open and closed issues

Is your feature request related to a problem? Please describe

A lot of Usenet users have the problem that they have limited retention with their unlimited provider and are using long retention block accounts for older usenet releases, so in general they want to avoid older nzbs if possible.

Additionaly, older files are missing articles more often than newer ones so you end up wasting bandwidth and time by trying older uploads first. Example of this happening:
grafik
(the screenshot is not showing the whole history, this goes on for a while)
If Sonarr would've picked the newest upload of this release at the beginning there wouldn't be any failures.

Describe the solution you'd like

Compare releases with the same title and roughly the same size by age:

Before:
grafik
After:
grafik

Describe alternatives you've considered

An "Old Age Penalty" setting where you can set the number of days after which a nzb get's a penalty for being too old under Settings->Indexers. Not a big fan of this though as this just solves the problem of using block accounts when it wouldn't be necessary.

Anything else?

I already created a possible solution (I didn't want to create PR here without an issue):
PCJones#1

@markus101
Copy link
Member

markus101 commented Sep 30, 2023

You opened the PR (#6056) before the opening this GHI, the GHI is helpful, but after the PR is open and these details could have been added there.

@markus101
Copy link
Member

I don't think title should have any bearing on things, it works in this example. but it's going to lead to unexpected and hard to troubleshoot behaviour. The reason Sonarr considers size is due to par2 files, generally in similar releases differing in sizes the larger has par2 files and the smaller does not, your examples have quite different sizes.

The other issue is different backbones for usenet are going to have different results, while the youngest one worked for you, it doesn't mean it's the only one that will work and in my testing the releases in the 800+ days range have no issues completing.

A preferred age/preferred maximum age would allow for releases that are within a shorter retention period to be grabbed over old ones, without over complicating things.

Also your fork is Sonarr-Extended? 🤔

@markus101 markus101 changed the title Sort equal usenet releases by age Ability to Prefer Newer Usenet Releases Sep 30, 2023
@PCJones PCJones mentioned this issue Sep 30, 2023
2 tasks
@mynameisbogdan
Copy link
Contributor

Also your fork is Sonarr-Extended? 🤔

Sonarr-Enhanced 👍

@zw7u9tru
Copy link

zw7u9tru commented Dec 5, 2023

In my case I have 2 providers with mediocre retention but lots of connections, then I have a super slow backup provider with great retention but only 2 connections. It would be great if age could be sorted on so I don't get stuck using my backup provider every download.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants