Shield interactive indexing from bulk-reindex throttling
Shared capacity can look healthy while individual workloads still interfere with one another.
Protecting interactive updates may require different treatment than large scheduled rebuilds.
“Our rebuild can take longer; stale stock during the day is the part that hurts.”
Margaret Dekker · Search Infrastructure Engineer
Runs catalog synchronization for a national retailer whose pricing and availability changes must remain searchable during nightly rebuilds.
What pulls against what
- interactive freshness vs. bulk throughput
- tenant fairness vs. utilization efficiency
- platform defaults vs. operational exceptions
What is at stake
A few scheduled rebuilds are causing avoidable throttling for time-sensitive updates. Better isolation protects customer freshness without abandoning bulk throughput
Why Algolia
At Algolia, this matters because indexing workloads can combine continuous updates with large catalog changes.
Written for
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.