Some part of the server-side work is linear in the number of hits.
It has to look up field values for each one of those hits, and that
is linear.
At some level, you've got one lookup for each term in the query and
one lookup for each hit. If you have a handful of terms and
a 1000 hits, the time is probably dominated by the number of hits.
I agree with the advice "get what you need".
wunder
On 4/29/09 5:30 AM, "Michael Ludwig" wrote:
> Wouter Samaey schrieb:
>
>> Can someone please comment on the performance impact of the number of
>> search results?
>> Is there a big difference between querying for 1 result, 10, 20 or
>> even 100 ?
>
> Probably not, but YMMV, as the question is very general.
>
> Consider that for fast queries the HTTP round trip may well be the
> determining factor. Or XML parsing. If you've stored a lot of data in
> Solr and request all of it to be returned, the difference between 1 and
> 100 results may be the difference between 1 and 100 KB payload.
>
> If you think it matters, the best thing for you would be to do some
> profiling for your specific scenario.
>
> The rule of thumb here is probably: Get what you need.
>
> Michael Ludwig