playbook/antigravity-awesome-skills/skills/vercel-optimize/references/support-topics/database-egress-pooling-region.md

id	title	status	candidateKinds	frameworks	priority	citations	maxBriefChars
database-egress-pooling-region	Database region and connection pressure	active	slow_route	*	60	https://vercel.com/docs/regions https://vercel.com/docs/functions https://vercel.com/docs/functions/functions-api-reference/vercel-functions-package https://vercel.com/docs/functions/limitations	800

Investigation Brief

Only recommend database or region changes when source and metrics both point to downstream I/O rather than in-process compute.

Evidence To Check

Compare cpu.p95 with latency.p95, then inspect database awaits, query fan-out, connection creation, pool lifecycle handling, and configured regions in project files.

Do Not Recommend When

Do not name a database provider, pooling product, or region change unless the repo and project config prove it applies.

Verification

Tie the finding to the observed wall-clock gap and the exact query, pool, or region configuration line.