VersionControl:PRs/maybelle-config/252: Difference between revisions
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
cryptograss/maybelle-config#252, as GitHub has it |
cryptograss/maybelle-config#252, as GitHub has it |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
|url=https://github.com/cryptograss/maybelle-config/pull/252 | |url=https://github.com/cryptograss/maybelle-config/pull/252 | ||
|author=magent-cryptograss | |author=magent-cryptograss | ||
|state= | |state=merged | ||
|base=production | |base=production | ||
|branch=memory-lane-cache-volume | |branch=memory-lane-cache-volume | ||
|opened=2026-11-01 04:18:12 | |opened=2026-11-01 04:18:12 | ||
|pushed=2026-11-01 04:17:52 | |pushed=2026-11-01 04:17:52 | ||
|merged= | |merged=2026-11-01 05:21:18 | ||
|closed= | |closed= | ||
|worked_on_by=magent, justin | |worked_on_by=magent, justin | ||
| Line 16: | Line 16: | ||
|deploy=redeploy maybelle | |deploy=redeploy maybelle | ||
}} | }} | ||
<pre class="pr-body">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</pre> | |||
Latest revision as of 18:06, 9 November 2026
| 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