On 5/15/06, Marcus Stratmann <[EMAIL PROTECTED]> wrote:
The only situation I get OutOfMemory errors is after an optimize when the server performs an auto-warming of the cahces:
A single filter that is big enough to be represented as a bitset (>3000 in general) will take up 1.3MB Some ways to help memory: - increase the heap size ;-) - make sure you don't have autowarming for more than one searcher happening at a time. If this happens, you should see something in your logs like "PERFORMANCE WARNING: Overlapping onDeckSearchers=2" - do omitNorms on every field you can... every field with norms will take up 1 byte per document (11MB in your case) - make caches smaller if you can survive the performance hit... A single filter that is represented as a BitSet will take up 1.3MB for 11M docs (and bigger in the case that maxDocs is larger tha numDocs because of deletions). -Yonik
