Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: local policy)
To: solr-user@lucene.apache.org
MIME-Version: 1.0
Subject: About enableLazyFieldLoading and memory
Message-ID: 
 <OF2D64B35D.2DE6EDB0-ONC1257C9F.00292114-C1257C9F.002A7BF1@correo.aeat.es>
From: david.davila@correo.aeat.es
Date: Tue, 18 Mar 2014 08:44:02 +0100
Content-Type: multipart/alternative;
 boundary="=_alternative 002A7BEFC1257C9F_="

--=_alternative 002A7BEFC1257C9F_=
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="ISO-8859-1"

Hello,

we have a Solr Cloud 4.7, but this question is also related with other=20
versions, because we have tested this in several installations.


We have a very big index ( more than 400K docs)  with big documents, but=20
in our queries we don't fetch the large fields in fl parameter. But, we=20
have seen that memory grows when we look for big documents because of the=20
Document Cache. This only happens in some queries we have to do, with=20
maybe more than 1000 docs in the response. We have set=20
enableLazyFieldLoading to true, so, we think that Document Cache should=20
grow more or less the same with all documents because we only fetch ID=20
field.

My question is: What does Solr exactly do when enableLazyFieldLoading is=20
set to true? Why does the size of the document have an influence in the=20
memory consumption?


Thanks in advance,

David D=E1vila Atienza
AEAT - Departamento de Inform=E1tica Tributaria
Subdirecci=F3n de Tecnolog=EDas de An=E1lisis de la Informaci=F3n e Investi=
gaci=F3n=20
del Fraude
Tel=E9fono: 917681160
Extensi=F3n: 30160
--=_alternative 002A7BEFC1257C9F_=--