How can I use Hoppscotch to measure and isolate server‑side processing time for a GraphQL query before optimizing?
0 reputation · 03 Jan 2020, 18:11 UTC
I send a GraphQL request through Hoppscotch and observe the total response time displayed in the UI. I need to understand how much of that latency is due to network factors (DNS, TCP/TLS handshake) versus actual server execution so I can pinpoint the bottleneck before making backend changes.
Does Hoppscotch provide separate timings for DNS lookup, TCP connect, TLS handshake, and server‑side processing? If not, what is the recommended approach within Hoppscotch to estimate the server‑side component? Finally, can I enable any built‑in profiling or export a trace similar to a HAR file to analyse the timing breakdown?