Visualizers

Learn by moving things

Interactive explainers for the ideas behind retrieval, embeddings, and agents. A formula tells you what is true; dragging a vector shows you why. Each one also appears inside the article it belongs to, and runs entirely in your browser, so drag, poke, and break it.

Portrait of Sachin Gupta rendered in binary

A push CDN uploads content to every edge at deploy time, before anyone asks. Even the first request in a region is a hit, because you paid the cost up front. Good for high-traffic, stable assets.

Push CDN: pre-stock every edge ahead of timeauto
origindeployedge 1stockededge 2stockededge 3stockedpush at deploy

At deploy time you upload the file to every edge, before anyone asks for it.

The cache key decides what counts as the same request. By default it is the whole URL, so ?utm=fb and ?utm=tw become separate copies and wreck the hit rate. Normalize the key to ignore marketing params.

The cache key: what counts as the same requestauto
/logo.pngkey →slot A
/logo.png?utm=fbkey →slot B
/logo.png?utm=twkey →slot C
distinct cached copies: 3

By default the key is the whole URL, so ?utm=fb and ?utm=tw look like different files. Three near-identical requests, three separate copies, a wrecked hit rate.

When a popular file expires everywhere at once, every edge would hit the origin together. An origin shield is one mid-tier node all edges fetch through, so the origin sees a single request. The thundering herd at CDN scale.

Origin shield: one fetch to the origin, not one per edgeauto
edge 1edge 2edge 3edge 4edge 5origin5 hits at once

Without a shield, when a popular file expires everywhere at once, every edge fetches it from the origin at the same moment. Five edges, five simultaneous origin hits.

Visualizers — Sachin Gupta