BTW this applies for 4.0-dev. In 3x the String instance from a
StringIndex is directly used, this is then put into a list. So there
is no extra object instance created per group matching the query.
Martijn
On 12 November 2011 08:49, Rafał Kuć wrote:
> Hello!
>
> Thanks, that's what I was looking
Hello!
Thanks, that's what I was looking for :)
--
Regards,
Rafał Kuć
http://solr.pl
> The ngroup option collects per search the number of unique groups
> matching the query. Based on the collected groups it returns the
> count.
> So it depends of the number of groups matching the query.
> To
The ngroup option collects per search the number of unique groups
matching the query. Based on the collected groups it returns the
count.
So it depends of the number of groups matching the query.
To get more in detail: per unique group a ByteRef instance is created
to represent a group and this put
Hello!
I was wondering if there is a way for calculating the memory
consumption of group.ngroups parameter. I know the the answer can be
'that depends', but what I'm actually wondering about is what the
memory consumption depends on - number of documents returned by a
query or number of groups ? O
