polls: don't continuously refresh closed polls and refresh less frequently #472

Merged

Oneric merged 2 commits from Oneric/akkoma-fe:poll-upd-frequency-reduction into develop

2026-01-24 18:30:00 +00:00

Oneric commented

2026-01-14 01:42:55 +00:00

Owner

Refreshing closed polls makes no sense, and as for refresh frequency:

Thirty seconds is much quicker than any other auto-refreshes in the
interface. Emitting a request for every users and tab with the poll
loaded this frequently can add up to a noteworthy total on the backend.

This is significantly worsened by our backend currently synchronously
fetching and updating the status of remote polls when queried about
while initiating a remote fetch for every incoming request inbetween
the last refetch passing the age threshold and the first current fetch
suceeding and completing its db transaction.

Refreshing closed polls makes no sense, and as for refresh frequency: > Thirty seconds is much quicker than any other auto-refreshes in the interface. Emitting a request for every users and tab with the poll loaded this frequently can add up to a noteworthy total on the backend. > > This is significantly worsened by our backend currently synchronously fetching and updating the status of remote polls when queried about while initiating a remote fetch for every incoming request inbetween the last refetch passing the age threshold and the first current fetch suceeding and completing its db transaction.

Oneric added 2 commits

2026-01-14 01:42:56 +00:00

polls: reduce frequency of update fetches 8d8e6d979a

Thirty seconds is much quicker than any other auto-refreshes in the
interface. Emitting a request for every users and tab with the poll
loaded this frequently can add up to a noteworthy total on the backend.

This is significantly worsened by our backend currently synchronously
fetching and updating the status of remote polls when queried about
while initiating a remote fetch for every incoming request inbetween
the last refetch passing the  age threshold and the first current fetch
suceeding and completing its db transaction.

polls: do not fetch updates for closed polls

ci/woodpecker/pr/woodpecker Pipeline failed

Details

ci/woodpecker/pull_request_closed/woodpecker Pipeline was successful

Details

9bfd3936d6

Oneric commented

2026-01-24 18:29:55 +00:00

Author

Owner

since nobody complained i assume 150s refresh interval is fine (for now, can be lowered again to e.g. a minute (but not 30s, that’s excessive)) once the backend is actually fixed to dedupe refreshes and perform them async