fix(albok-service): 0.1.6 on nh3-docker (review fold: locked index build)

This commit is contained in:
vh
2026-10-04 05:45:25 -07:00
parent 957cd80d5e
commit 2449e8806f
2 changed files with 6 additions and 3 deletions
+5 -2
View File
@@ -6,8 +6,11 @@ The FastAPI process that owns Albok's buildings-and-wings store (`vh/albok`,
- **URL:** `http://albok.nh3.internal:8392` (= `http://10.100.50.40:8392`). Container port 8390.
⚠ Host port **8392**, because **8390 on nh3-docker is the althing post office**.
- **Image:** `gitea.phasefinal.com/pfi/albok-service:0.1.5` @ `sha256:dde3303d…` (pinned in `compose.yaml`), built
2026-10-03 ~2038 from vh/albok `e70321c` (tags albok-service/v0.1.5 + core v0.1.3; pushed by infra-ops on Prime's go).
- **Image:** `gitea.phasefinal.com/pfi/albok-service:0.1.6` @ `sha256:2b44c9d4…` (pinned in `compose.yaml`), built
2026-10-04 ~0544 from vh/albok `6c1adcd` (tags albok-service/v0.1.6 + core v0.1.4; pushed by infra-ops on Prime's go). 0.1.6 is
the review fold on 0.1.5's search fix: the keyword-index build now takes a lock (two concurrent first queries could cross
ids or KeyError), the core search keyword is keyword-only (do not pin albok 0.1.3), and the store wrapper fails closed.
0.1.5 (below) was built 2026-10-03 ~2038 from `e70321c` (tags albok-service/v0.1.5 + core v0.1.3).
0.1.5 = search speed: an index on the facet table's object_id and one cached keyword index per wing (fleet/memory query 4.5 s → ~0.25 s warm;
the first search per wing after a start or an ingest rebuilds the keyword index, ~1.7 s). The facet index is built at the first open (~0.35 s, +17 MB).
**Measured live by albok-dev 2026-10-03 ~2245** (same idle container, before/after): fleet/memory top-5 median 3.97 s → **0.22 s** (n=5;