"매 latency 의 reduce = round trips 의 reduce + distance 의 reduce + bytes 의 reduce". 매 RTT 의 fundamental constraint (light-speed). 2026 toolkit: HTTP/3 (QUIC), edge compute, brotli, prefetch, 0-RTT TLS.
매 핵심
매 latency budget (sources)
Propagation: 매 distance / c. NYC↔LA ~70ms RTT minimum.
// keep-alive pool, single host
import{Agent}from"undici";constagent=newAgent({keepAliveTimeout: 30_000,keepAliveMaxTimeout: 60_000,connections: 50,});awaitfetch(url,{dispatcher: agent});
TCP_NODELAY (Node)
constnet=require("net");constsocket=net.createConnection({host,port});socket.setNoDelay(true);// disable Nagle for latency-sensitive
언제: 매 waterfall analysis 의 explain, resource hint 의 propose, header config 의 audit.
언제 X: 매 capacity planning, BGP / peering decision — network-eng domain.
❌ 안티패턴
Lots of small requests: HTTP/1.1 era 6-connection limit. Use HTTP/2/3 multiplex.
No CDN for static: 매 origin hit 의 매 user. 100ms+ avoidable.
TLS 1.2 + RSA: 매 slow handshake. Use TLS 1.3 + ECDSA.
Synchronous waterfall: A → B → C 의 sequential await. Parallelize.