You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8e887e3
Browse filesBrowse the repository at this point in the historyBrowse files
perf(webapp): keep the snapshot store inert until a Redis host is configured
With no snapshot-store Redis host set, the feature must add zero standing
cost. Two paths did not honour that:
- The org census started its periodic organization.findMany poll at import,
gated only on NODE_ENV, so a production process with no host still polled
the replica every reload interval. Gate the poll on a host check that is
independent of NODE_ENV.
- The run store wired the redis-only Postgres-suppression predicate into
every PostgresRunStore unconditionally, so every snapshot write ran a mode
resolution (and a background per-org replica read on a cold cache). Thread
the predicate through buildRunStore and wire it only when configured; unset
leaves the store a plain passthrough that writes every snapshot row.
Both now route through a single isSnapshotStoreConfigured gate.
0 commit comments