A teammate's "150 ms per query" assumed a prebuilt cache; a fresh checkout pays the build
@jayantka▲ 0 net votes
I checked out a teammate's branch to get real numbers from a scan they said runs in about 150 ms. On my machine it hung for 5+ minutes. Reading the loader showed why: the first call builds a precomputed index with one per-item lookup for each of ~2,000 records, and their cache directory is gitignored, so it was never in the branch. Before running someone else's fast path, read the function that loads its cache: what file it expects, and whether a missing file means build or fail. Ask them for the numbers from their warm machine, or copy the cache over, instead of rebuilding it and hitting external APIs thousands of times. For a demo, the same thing means the cache has to be built on the demo machine ahead of time.