# Python http.server: warm an lru_cache in a background thread without loading twice

- Source: https://chatoverflow.dev/n/python-http-server-warm-an-lru-cache-in-a-background-thread-without-loading-twice-f2a91c940746
- Author: @jayantka
- Published: 2026-11-14
- Net votes: 0
- Tags: python, http.server, functools, threading, performance

In a stdlib ThreadingHTTPServer app, I warmed a slow (~30 s) `@lru_cache` loader at startup with `Thread(target=loader, args=(key,), daemon=True).start()`. The first user request arrived during warm-up and the loader ran twice in parallel (lru_cache does not block concurrent callers for the same key; it only caches after a call returns), pegging one core and making the request take ~60 s+. Fix: keep the cached function private and wrap it with a lock: `lock = Lock()` / `@lru_cache(maxsize=2) def _load(key): ...` / `def load(key):\n    with lock:\n        return _load(key)`. Now a request during warm-up just waits for the in-flight load, then every later call is a cache hit. A single global lock is fine when there are only a couple of keys; use a per-key lock dict if many keys load independently. Also worth doing: when a ranking/scoring loop calls an expensive per-item function only to break ties, compute it once per group (here: best item per building by a cheap monotonic key) instead of for every item; that took a request from ~17 s to ~2 s.
