Private
Public Access
Push due-feed scheduling into an indexed DB query (C1)
poll_due_feeds loaded every active feed's timing fields and recomputed each one's error-backoff due-ness in Python on every beat tick (every 1-2 minutes) — scheduler CPU and DB reads grew linearly with total feed count regardless of how many were actually due. Feed.next_fetch_at (indexed together with is_active) is now set by fetch_feed itself right after every fetch attempt, success or error, using the same backoff formula that used to run per-feed in poll_due_feeds. The scheduler's query is now a direct indexed range scan (next_fetch_at <= now), ordered so the most overdue feeds claim first, and bounded to POLL_BATCH_SIZE so a large backlog spreads across several ticks instead of dispatching everything at once. A migration backfills next_fetch_at for existing feeds using the same formula. reset_feed_backoff also clears next_fetch_at so a manually-reset feed is immediately due again, matching its prior behavior. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
b84cfe6474
commit
b33fe905d2
6 files changed
+186
-50
No files matched your search
@@ -42,6 +42,15 @@ class Feed(models.Model):
|
||||
fetch_error_count = models.PositiveIntegerField(default=0)
|
||||
is_active = models.BooleanField(default=True)
|
||||
|
||||
# Set by fetch_feed right after every fetch attempt (success or error)
|
||||
# to last_fetched_at + effective_interval_minutes — precomputed once,
|
||||
# at write time, instead of poll_due_feeds re-deriving due-ness (which
|
||||
# depends on fetch_error_count's exponential backoff) for every active
|
||||
# feed on every tick (C1). NULL means "due now", same as a feed that's
|
||||
# never been fetched. Indexed with is_active below so the scheduler's
|
||||
# query is a direct index range scan, not a full table scan.
|
||||
next_fetch_at = models.DateTimeField(null=True, blank=True)
|
||||
|
||||
# Set by poll_due_feeds' atomic claim (an UPDATE ... WHERE clause, not
|
||||
# select_for_update — Celery Beat and fetch_feed run in separate
|
||||
# transactions) and cleared once fetch_feed finishes, so overlapping
|
||||
@@ -53,6 +62,9 @@ class Feed(models.Model):
|
||||
|
||||
created_at = models.DateTimeField(auto_now_add=True)
|
||||
|
||||
class Meta:
|
||||
indexes = [models.Index(fields=["is_active", "next_fetch_at"])]
|
||||
|
||||
def __str__(self):
|
||||
return self.title or self.feed_url
|
||||
|
||||
|
||||
Reference in new issue
Block a user