Just to reword what others have said, ES will allocate memory for [size] scores 
as I understand it (per shard?) regardless of the final result count. If you're 
getting back 4986 results from a query, it'd be faster to use "size": 4986 than 
"size": 1000000. 

What I've done in similar situations is to issue a count first with the same 
filter (which is very fast), then use the result of that in the size field. It 
worked much better/faster than using a default large size.

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/ef65d92f-9a9c-4206-a2b9-5b769e4cec87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to