sdcorejs-review-performance-nestjs

To detect N+1 queries in a NestJS backend, a performance audit counts queries per endpoint and flags list endpoints. This audit checks WHERE-filtered columns for missing indexes and surfaces slow queries using pg_stat_statements.

A performance budget gate for NestJS APIs is a pre-release check that audits backend performance against defined thresholds. It identifies missing indexes, risky migrations, connection pool issues, oversized payloads, and memory leaks before production deployment.

You audit connection pool sizing and memory leaks by running probes in a production-like environment to measure p50/p95/p99 metrics. This process evaluates pool exhaustion, blocking I/O, and memory behavior against performance budget thresholds.

Yes, you can use pg_stat_statements to find missing indexes in NestJS. A performance audit utilizes pg_stat_statements to surface slow queries and checks WHERE-filtered columns to identify missing indexes.

The best way to resolve API timeouts and slow DB queries in NestJS is running a performance audit gate. It produces Critical, Important, and Minor findings with file references, measurements, and query plan evidence for actionable fixes.