Also note that making RAMBufferSize too big isn't useful. Lucid recommends 128M as the point over which you hit diminishing returns. But unless you're having problems speed-wise with the default, why change it?
And are you actually getting OOMs or is this a background question? Best Erick On Mon, Mar 28, 2011 at 6:23 AM, Li Li <fancye...@gmail.com> wrote: > there are 3 conditions that will trigger an auto flushing in lucene > 1. size of index in ram is larger than ram buffer size > 2. documents in mamory is larger than the number set by setMaxBufferedDocs. > 3. deleted term number is larger than the ratio set by > setMaxBufferedDeleteTerms. > > auto flushing by time interval is added by solr > > rambufferSize will use estimated size and the real used memory may be > larger than this value. So if your Xmx is 2700m, setRAMBufferSizeMB. > should set value less than it. if you setRAMBufferSizeMB to 2700m and > the other 3 conditions are not > triggered, I think it will hit OOM exception. > > 2011/3/28 Isan Fulia <isan.fu...@germinait.com>: >> Hi all , >> >> I would like to know is there any relation between autocommit and >> rambuffersize. >> My solr config does not contain rambuffersize which mean its >> deault(32mb).Autocommit setting are after 500 docs or 80 sec >> whichever is first. >> Solr starts with Xmx 2700M .Total Ram is 4 GB. >> Does the rambufferSize is alloted outside the heap memory(2700M)? >> How does rambuffersize is related to out of memory errors. >> What is the optimal value for rambuffersize. >> >> -- >> Thanks & Regards, >> Isan Fulia. >> >
