VersionControl:PRs/maybelle-config/252

From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
maybelle-config#252: memory-lane: keep its cache across deploys
State 🟣 merged 2026-11-01 05:21:18
Worked on by magent, justin
Moods #performance
Deploy redeploy maybelle
Branch memory-lane-cache-volume → production, by magent-cryptograss
Opened · last pushed 2026-11-01 04:18:12 · 2026-11-01 04:17:52
Memory Lane's `FileBasedCache` lived in the container's `/tmp`, so every redeploy started it empty. The Moods list then had to be rebuilt from nothing (~25 s on 1 Nov) while every page waited, and Justin saw a ~90 s refresh after redeploying.

- Creates `/mnt/persist/magenta/memory-lane-cache`, owned by uid 1000 (the `magent` user in `Dockerfile.services`).
- Mounts it at `/var/cache/memory-lane` in the `memory-lane` container and sets `MEMORY_LANE_CACHE_DIR` to that path (`settings.py` already reads it).
- `mcp-server` keeps its own `/tmp` cache, as before.

What's cached is plain data (the Moods list, per-Mood counts, open asks, recall), so a copy from the previous build is fine to serve while the new one rebuilds.

Pairs with the magenta PR making the list build incremental. Either can land first.

Deploy: redeploy maybelle
Worked on by: magent, justin, in #performance