An interesting check would be disable compression on stored fields, and
to check if your searcher works better. Disable compression should
increase stored and searcher should be quicker.
I have read that disable compression all you need to do is to write a
new codec that uses a stored fields format which does not compress
stored fields such as Lucene40StoredFieldsFormat
<http://lucene.apache.org/core/4_0_0/core/org/apache/lucene/codecs/lucene40/Lucene40StoredFieldsFormat.html>.
Best regards
El 18/03/2014 14:47, Shawn Heisey escribió:
On 3/18/2014 7:18 AM, david.dav...@correo.aeat.es wrote:
yes, but if I use enableLazyFieldLoading=trueand my queries only request
for very small fields like ID, DocumentCache shouldn't grow, although my
stored fields are very big. Am I wrong?
Since Solr 4.1, stored fields are compressed. This probably means that
in order to get a tiny field out, it must still retrieve an an entire
block of compressed data and uncompress it.
The information in the issue that added the compression feature says
that only one compressed block is ever retrieved for a complete document.
https://issues.apache.org/jira/browse/LUCENE-4226
I wonder if perhaps either Solr or Lucene is dropping all the data into
one or more caches even though you only requested the ID, simply because
it is already available after decompression. This is only a guess, and
I hope I'm wrong. If this is indeed happening, it would defeat lazy
field loading. Can someone with a better understanding comment?
Thanks,
Shawn
