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

AniDB tasks are blocking the queue too much. It could be handled better. #1214

Closed
plato79 opened this issue Jan 4, 2025 · 2 comments
Closed

Comments

@plato79
Copy link

plato79 commented Jan 4, 2025

VERSION INFORMATION

Server Version: 5.0.0.0 Stable
(76da970)

Desktop Version: -

If you've compiled your own version, please use the last commit you compiled.

DESCRIPTION

When there are thousands of tasks in the queue and all of the workers are working on AniDB tasks the queue is emptied extremely slow. I believe that's because AniDB tasks are handled one by one.

STEPS TO REPRODUCE

This could happen entirely random when importing a lot of files.

POSSIBLE SOLUTION

At every 5-6 tasks processed, the worker tasks should be analyzed. If all of them are AniDB tasks or if it's bigger than a set value, then non-AniDB tasks should be brought forward of the queue ( around 8 tasks maybe ) . This way while anidb tasks are executed one by one as intended, shoko could take care of other tasks ( grabbing TMDB Image, trakt.tv data update etc.. ).

It should be checked constantly because after those 8 tasks are processed it may be possible that again 10+ anidb tasks are clumped together in front of the queue and blocking other tasks.

@harshithmohan
Copy link
Member

AniDB tasks are always done one by one, and other non-anidb tasks are not blocked by them if you have workers available 🤔

I will tag the experts: @revam @da3dsoul

@da3dsoul
Copy link
Member

da3dsoul commented Jan 4, 2025

Mohan is correct. I saw you are on the discord. You can ask more detailed questions there. I'll close this, as AniDB simply does not block other task types.

@da3dsoul da3dsoul closed this as completed Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants