Traffic and simultaneity
Measure searches per second and how many requests are active simultaneously. Split autocomplete, search and filters, because they have a different load profile. Use peaks per store and device instead of just daily averages.
Capacity planning
Plan capacity for growth and peaks, not for the current average.
Search tax doesn't just grow because of more visitors. Larger catalogs, additional stores, more complex filters and more frequent updates also require capacity. A useful plan connects technical boundaries to concrete growth scenarios.
Catalogue growth
Include products, variants, languages, stores and new index fields in forecasts. Increase more features increase both storage and processing and can make filters heavier. Test with realistic future volumes before reaching limits.
Indexing capacity
Plan separately for full imports and minor interim changes. Measure how quickly a backlog is eliminated while normal search traffic continues. A system that indexes quickly only without visitors does not provide reliable production capacity.
Safe spare capacity
Reserve space for campaigns, infrastructure failures and unexpected growth. Link warning boundaries to concrete scale actions. This way, it is not necessary to think during a peak which extension is safely possible.
Search management
Make reliability part of daily management.
Discuss which measurements, responsibilities and restoration routes fit your online stores and technical environment.