Menu

Debugging Exploded Embeddings Cost After Adding a Nightly Property Reindex
📰

Debugging Exploded Embeddings Cost After Adding a Nightly Property Reindex

DEV Community: backend·ArthurFinley2291·6 days ago
#5ibgGqA5
#devtobackend#devto#dev#embedding#vector
Reading 0:00
15s threshold

TL;DR: If embeddings cost exploded after adding a nightly property reindex, debug duplicate embedding calls first: put a content-hash gate immediately before embedding. The watcher should embed a chunk only when its normalized text hash differs from the hash stored with the current vector; otherwise, skip it. Treat embeddings_per_run as a reconciliation total, alert when it exceeds the changed-chunk count, and keep embedding plus vector writing behind an adapter so changing a provider does not change the watcher.

This architecture decision record addresses one narrow failure: a scheduled reindex quietly turns unchanged descriptions, amenity rules, and leasing notices into duplicate embedding calls.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.