dtourolleandClaude Opus 5 195388b2e3 Adopt faces a hundred images per commit, and hold one generation per image in the shards ...

The shard import recorded each adopted image in its own transaction:
fourteen thousand commits, and fourteen thousand turns at the write lock
that every read on the UI thread queued behind — the sync was felt as a
laggy grid and as "database is locked" from whichever writer lost the
wait. `record_detections_within` takes the caller's transaction, and the
import commits every hundred images.

The store carried every detector generation of an image — 24,123 entries
for 19,089 images on the reference library, a third of its 293 MB — when
only the strongest is ever adopted. A put now skips a pass a held one
outranks, and retires the passes it outranks from the index; sealed
shards keep their bytes, but nothing is written twice from here.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-20 22:31:47 +02:00

..

examples

Keep each face's quality, and never compare against a poor one

2026-09-11 21:50:12 +02:00

src

Adopt faces a hundred images per commit, and hold one generation per image in the shards

2026-09-20 22:31:47 +02:00

Cargo.toml

Sync face data as sealed shards, so a second device does not re-index

2026-08-26 22:41:50 +02:00