On May 13, 2009, at 6:53 PM, vivek sar wrote:
Disabling first/new searchers did help for the initial load time, but
after 10-15 min the heap memory start climbing up again and reached
max within 20 min. Now the GC is coming up all the time, which is
slowing down the commit and search cycles.
This is still puzzling what does Solr holds in the memory and
doesn't release?
I haven't been able to profile as the dump is too big. Would setting
termIndexInterval help - not sure how can that be set using Solr.
It would have to be set in the same place that the ramBufferSizeMB
gets set, in the config, but this would require some coding (albeit
pretty straightforward) to set it on the IndexWriter. I don't think
it would help in profiling.
Do you have warming queries? (Sorry if I missed your answer)
Also, I know you have set the heap to 8 gbs. Is there a size you can
get to that it levels out at? I presume you are getting Out Of
Memory, right? Or, are you just concerned about the current mem. size?
