The control-plane watch is implemented as a 250 ms database poll per subscription. An idle instance therefore runs about 200 transactions a second, almost all sequential scans of the 28-row resources table; the transaction counter and buffer activity are dominated by it rather than by real work.
Wanted: replace the per-subscriber polling with a push path — LISTEN/NOTIFY from the resource write, or one shared poller in the State Store that fans out to streams — while keeping the same watch contract (resume from a version, no missed update).
Done when: an idle instance's transaction rate drops to a small baseline and a resource change still reaches every watcher promptly.
The control-plane watch is implemented as a 250 ms database poll per subscription. An idle instance therefore runs about 200 transactions a second, almost all sequential scans of the 28-row resources table; the transaction counter and buffer activity are dominated by it rather than by real work.
Wanted: replace the per-subscriber polling with a push path — LISTEN/NOTIFY from the resource write, or one shared poller in the State Store that fans out to streams — while keeping the same watch contract (resume from a version, no missed update).
Done when: an idle instance's transaction rate drops to a small baseline and a resource change still reaches every watcher promptly.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The control-plane watch is implemented as a 250 ms database poll per subscription. An idle instance therefore runs about 200 transactions a second, almost all sequential scans of the 28-row resources table; the transaction counter and buffer activity are dominated by it rather than by real work.
Wanted: replace the per-subscriber polling with a push path — LISTEN/NOTIFY from the resource write, or one shared poller in the State Store that fans out to streams — while keeping the same watch contract (resume from a version, no missed update).
Done when: an idle instance's transaction rate drops to a small baseline and a resource change still reaches every watcher promptly.