Feeds are fetched one at a time, so a refresh waits on every site in turn #104
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fetching feeds is now 65-90% of a scan (traces 69b2e9b9..., 533a9fe1..., e3f0e97d..., 2026-09-29): 13 s of fetches in a 20 s refresh of 32 feeds, 18 s of 19.6 s in a scheduled scan of 67. Each feed waits for the one before; toddstashwick's redirect loop alone takes 4.8 s. While a scan runs, a 'download this now' request queues behind it. Fetching the due feeds' bodies a few at a time before handling them in order would cut that to about the slowest few sites.
Fixed in
7a134b8: a scan fetches the due feeds' bodies up to six ahead, in tasks of their own, and handles each in order as before; Patreon creators still fetch in scan_one. Tests pass on SQLite and Postgres and in the browser suite. Deployed 2026-09-29 20:29; no scan had checked a feed yet to compare against the 20 s refresh (69b2e9b9...).