: We recently decided to move from Solr version 3.5 to 4.2.1. The transition
...
: Most of the fields are multiValued (type String) and the size of array in
: those vary from 5 to 50K. So our 30% of popular documents are tall. Not all
...
: Issues that we observed is high CPU and Memory utilization while retrieving
: these document with large multivalued fields.
Are you certain you ar using 4.2.1 and not 4.2 ?
There was a particularly bad bug related to "enableLazyFieldLoading"
affecting Solr 4.0, 4.1, and 4.2, but it should *not* affect 4.2.1...
https://issues.apache.org/jira/browse/SOLR-4589
If you are seeing slow response times and heavy CPU spikes, it would help
to know if you could take some thread dumps during those CPU spikes to see
what it chewing up CPU ... you may just be seeing the effects of stored
field compression -- which uses more CPU on stored field retrieval to
decompress the blocks of field values, but allows the index size to be
much smaller so more things can be cached in RAM.
: So my questions is if its possible to make this tall document to a wide
: document so only required information is fetched. Is this a better
: approach to look for? Any other thoughts are welcomed.
I don't really understand what you mean by "tall" vs "wide" (i thought i
understood what you ment by "tall" initially, but i don't understand what
you mean by "make the tall document side"
just in case it's not obvious: if there are stored fields you don't want
back in the response, leave them out of your "fl" param and only request
the fields you actaully want.
-Hoss
