plain-optimize

To fix N+1 query issues, you need to capture request traces using an observer tool, parse the JSON output for query counts and duplicate spans, and apply targeted optimizations to your database interactions.

Debugging slow page response times involves capturing observable request traces to reveal query counts, identifying duplicate queries or missing indexes, and applying performance fixes with a verification step.

Capture traces by enabling tracing on target requests using the observer request command, then parse the resulting JSON outputs to analyze query_count, duplicate_query_count, and spans for performance bottlenecks.

Yes, observer request tracing includes a verification step that allows you to capture a new trace after applying performance fixes to confirm the query count and response times have improved.

A high duplicate query count in trace spans typically indicates N+1 query patterns or missing database indexes, which you can identify by analyzing the captured observer request JSON outputs.

No, you enable tracing on specific target pages that exhibit slow response times or high query volumes to capture the necessary JSON outputs for analyzing missing indexes and slow database interactions.