-
-
Notifications
You must be signed in to change notification settings - Fork 132
Description
Problem description
When a newly released title is searched:
Few torrents are found initially
These torrents are cached by Comet
None are cached on the debrid service
After a few hours, new torrents appear that may be cached on debrid
However, for 7 days (LIVE_TORRENT_CACHE_TTL), no refresh happens because the cache is considered "fresh"
Example scenario:
Day 1: Search for a new movie → finds 3 torrents, none cached on debrid → cached by Comet
Day 2: 10 new torrents appear, some cached on debrid
Days 2-7: No refresh because cache is still "fresh" → users only see the original 3 uncached torrents
Proposed solutions
Solution 1: Shorter TTL when no torrents are cached on debrid
Add a new setting that applies a shorter TTL when no torrents are cached on debrid, even if torrents exist in Comet's cache, triggering a live scrape more often.
Solution 2: Dynamic TTL based on release date
Use the existing digital_release_cache table to apply a shorter TTL for recently released content resulting in a more aggressive scraper int he first X days of the release media
Do you think this can be a good idea or am I missing something?
I can help with the implementation.
We can also uso the solution 1 as fallback for the solution 2.