mmmmm DocValues actually is an un-inverted index that is built as part of the segment. This means that it has the same behaviour of the other segments files. Assuming you are indexing not a compound segment file but a classic multi filed segment in a NRTCachingDirectory, The segment is built in memory , and when it reaches the ramBufferSizeMB/ Hard commit it is flushed to the disk.
This means that in my opinion there is no particular observation of memory degradation in using the DocValues. I would actually say that using DocValues instead the old FieldCache is decreasing the memory consumption, as FiedlChaces are completely in memory ( with the expensive un-inverting process) >From Solr wiki : " In Lucene 4.0, a new approach was introduced. DocValue fields are now column-oriented fields with a document-to-value mapping built at index time. This approach promises to relieve some of the memory requirements of the fieldCache and make lookups for faceting, sorting, and grouping much faster. " I would manage memory more accordingly to the other feature you will use ! Let me know if I satisfied your curiosity! Cheers 2015-06-11 15:38 GMT+01:00 adfel70 <adfe...@gmail.com>: > I am using DocValues and I am wondering how to configure Solr's processes > java's heap size: does DocValues uses system cache (off heap memory) or > heap > memory? should I take DocValues into consideration when I calculate heap > parameters (xmx, xmn, xms...)? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/DocValues-memory-consumption-thoughts-tp4211187.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- -------------------------- Benedetti Alessandro Visiting card : http://about.me/alessandro_benedetti "Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry?" William Blake - Songs of Experience -1794 England
