Hi Mikhail, Thank a lot for your answer, this means we will only pay a small heap price for both docValues and indexed, right? Thx for your `rawSize=true` finding, this will be helpful to inspect disk usage.
Best, Heinz Am Di., 7. Feb. 2023 um 21:21 Uhr schrieb Mikhail Khludnev <m...@apache.org >: > Hello, Heinz. > These data structures reside on disk and only small excerpts ie head is > kept in heap. So, dropping them you should get some gain in heap, but I > don't think it's a lot. Indexing footprint should be reduced as well. > Regarding heap size. I've found a pretty cool param rawSize=true in > > http://localhost:8983/solr/admin/collections?action=COLSTATUS&collection=gettingstarted&coreInfo=true&segments=true&fieldInfo=true&sizeInfo=true&rawSize=true > which estimates field size, but it's a disk size, not heap usage. It seems > to me that heap size estimation is abandoned. > > On Tue, Feb 7, 2023 at 2:34 PM Heinz Hölzer > <heinz.hoel...@googlemail.com.invalid> wrote: > > > Hi, > > > > We are currently optimizing and cleaning up our complex Solr Schema and > we > > are wondering if the corresponding data structures of a field with > > indexed="true" and docValues="true" (inverted index, column-oriented > > mapping) are loaded from disk into memory when both features are never > used > > or accessed? In other words, can we decrease our memory usage by setting > > indexed and docValues to false even if those features are never used at > > runtime? > > > > Thx and best regards, > > Heinz > > > > > -- > Sincerely yours > Mikhail Khludnev > https://t.me/MUST_SEARCH > A caveat: Cyrillic! >
