Skip to content- Sources: primary
- Summary: Customer builds that passed the literal string VERCEL_GIT_COMMIT_SHA as the release name put every build into one release, and the worst case held 13,595 bundles and 44 million URL index rows that a single lookup could not scan before the query timeout, after which Symbolicator retried. Sentry capped each lookup at 1,000,000 rows and cached the miss, split a multi-table debug ID join into three single-table queries, stopped indexing generated file names, and turned off Postgres JIT, which had cut one query from 14.5 ms to 0.12 ms. Busy sessions on the main host fell 77% and lookup timeouts fell 98%, and Sentry JavaScript SDK 11.9.0 now ignores a commit variable whose value is its own name.
- Why it matters: It shows that bounding work per request fixed a Postgres load problem that bigger instances and extra indexes had not, and it gives a check for misnamed CI releases.
- Background: Symbolication maps minified JavaScript stack frames back to original source using uploaded source maps. Sentry finds the right map either by a debug ID stamped into each built file or, for older setups, by matching release name plus file URL through a large index table. Postgres JIT compiles expensive query plans to machine code, which pays off for long analytic queries but can cost more than it saves on short ones.