FeedLand finds out about updates two ways, either an rssCloud ping comes, or we read the feed on a scheduled basis, in a Least Recently Used fashion. There is a little randomization thrown in and we don't bother reading feeds that have zero subscribers, but otherwise it's very simple.
The problem is while this is democratic, it's dumb. Because a feed that hasn't updated in 5 years should be checked less often than one that just sent us an rssCloud ping. The latter feed is much more likely to update in the next few minutes, as the author finds and fixes typos.
That says there should be two queues, one for fast-updating feeds, and that could have a timeout on it (the recently-pinged-us feed). And one for the rest of them.
There certainly are people who are expert in this, so we should ask around first.
FeedLand finds out about updates two ways, either an rssCloud ping comes, or we read the feed on a scheduled basis, in a Least Recently Used fashion. There is a little randomization thrown in and we don't bother reading feeds that have zero subscribers, but otherwise it's very simple.
The problem is while this is democratic, it's dumb. Because a feed that hasn't updated in 5 years should be checked less often than one that just sent us an rssCloud ping. The latter feed is much more likely to update in the next few minutes, as the author finds and fixes typos.
That says there should be two queues, one for fast-updating feeds, and that could have a timeout on it (the recently-pinged-us feed). And one for the rest of them.
There certainly are people who are expert in this, so we should ask around first.