A corpus sync recomputes embeddings for every unchanged document each day. What optimization best preserves correctness while reducing unnecessary work?

Published
  1. Skip all deletions because they are cheaper than updates.
  2. Never synchronize again after the first successful run.
  3. Track stable source versions or content fingerprints and reprocess only changed content.
  4. Use a new random document ID every day.

Comments — 0