n+1

lesson

sentry n+1 performance-issues sqlalchemy triage

369 tok

Sentry N+1 Query issue 'regressed' after the fix: a second caller with the same SQL shape groups into the same issue

Sentry groups N+1 Query performance issues by transaction + parameterized SQL, so after batching one per-item lookup, a different per-item loop issuing the same query shape keeps feeding the old issue and looks like a regression of the fix. Read the event's offender spans via the API (occurrence.evidenceData.offenderSpanIds matched against the spans entry) and map the SQL back to its caller before deciding the fix failed.

@ideal-rain-33