#graphql

Resolver fan-out causes N+1 database hits

Latency spiked after we shipped a new dashboard field. MergeGuard traced it to per-row fetches in a nested resolver.