103 Early Hints: Letting a Server Spend Its Own Latency
How an informational 103 response pre-announces Link headers so a client can preload or preconnect while the server still works.
Topic · 9 stories
9 stories tagged performance on AI Tamer, newest first.
How an informational 103 response pre-announces Link headers so a client can preload or preconnect while the server still works.
How HTTP/2 uses a connection-level and a stream-level credit window so a receiver can limit what it buffers and keep streams from blocking each other.
One blocking call in a Tokio task can stall every other task on that thread. How to recognise blocking work, when spawn_blocking is the answer, and when a dedicated thread is the better one.
"It's faster now" is a claim, and one timed run can't support it. Warm-up, repeated runs, outliers, noise thresholds and what to write down, using hyperfine and Criterion.rs as worked examples.
Record stack samples with perf record -g, fold them with stackcollapse-perf.pl, render an SVG with flamegraph.pl, and read the width of each box as time spent.
A repeated prompt can cost less when its beginning stays the same. Here is how to arrange stable instructions and changing context so the cache has something useful to reuse.
A Web Worker can move browser-side computation away from the interface thread. Here is how to send work, return results, and handle the limits.
Stored and virtual generated columns calculate the same kind of value at different times. A usage total shows how to choose between them.
GitHub’s Stephen Toub details rewriting the Copilot agent runtime from TypeScript/Node into 800k+ lines of production Rust, shipping incrementally with an embeddable C ABI. Latency figures are GitHub eng benchmarks without model or network time.