Performance implications of `index.max_result_window` vs `track_total_hits`

Elastic Stack Elasticsearch
1

Hello,

For example, if we would have 50.000 results for a search query. If we really need to return an exact total number of matches and we enabled track_total_hits to get it. Should we just as well increase the max_result_wndow as we are already always counting all the records?

I guess the underlying question is - is retuning say the last 100 results (from 49.900 to 50.000) more intensive as opposed to the first 100 results (0 to 100) if we are already always counting all the records (as track_total_hits is true)?

Any insight would be appreciated,
Thanks

2

Welcome!

Should we just as well increase the max_result_wndow as we are already always counting all the records?

No.

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.