Most engaged issues whose comments are read directly per run when the
comment search misses them (#1862). Only issues the batched lookup found
open and updated since the engagement count; each costs its comment pages,
ETag-cached, so a quiet day is mostly 304s. The cap bounds a first run for
a user with many active claims. Most recently updated issues come first,
so an issue that gets a new comment moves to the front on the next run,
but one that stays quiet behind a hundred busier ones is not read until
the busier ones settle. That is why hitting the cap is a warning.
Most engaged issues whose comments are read directly per run when the comment search misses them (#1862). Only issues the batched lookup found open and updated since the engagement count; each costs its comment pages, ETag-cached, so a quiet day is mostly 304s. The cap bounds a first run for a user with many active claims. Most recently updated issues come first, so an issue that gets a new comment moves to the front on the next run, but one that stays quiet behind a hundred busier ones is not read until the busier ones settle. That is why hitting the cap is a warning.