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 21ffa6d
Browse filesBrowse the repository at this point in the historyBrowse files
authored
perf(issues): Reuse the group when fetching escalation forecasts (#127719)
Avoid reloading the group just to check `should_detect_escalation()`
when fetching an escalation forecast, both callers already have it. The
lookup was left over from when the check took an organization behind a
flag (#70443).
This runs for events on issues archived until escalating, roughly 30M
times a week in post_process at ~2ms p50, around 17 hours of db time a
week (ballpark) so again a pretty small change. [Example
trace](https://sentry.sentry.io/explore/traces/trace/d1138b8a7a8248d4b28a7f349b10225f/?node=span-91f7b1de6e7f52a1),
the `sentry_groupedmessage` select under `process_snoozes` is the one
that goes away.
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
0 commit comments