A little bit of description on the term heavy pressure might help? Does this involve concurrent read operations/ write operations or both?
Also some other things that effect performance: 1. What jvm parameters are set? 2. Do you have any custom index configurations set? 3. What does you repostiory.xml look like? This background info might help with answering your question. On Mon, Nov 23, 2015 at 8:13 AM, Roll, Kevin <[email protected]> wrote: > We have started to encounter OutOfMemory errors on Jackrabbit under heavy > pressure (it's worth noting that we are using the full Sling stack). I've > discovered that Lucene keeps a full index of the repository in memory, and > this terrifies me because we are already having problems just in a test > scenario and the repository will only grow. Unfortunately we are forced to > run this system on older 32-bit hardware in the field that does not have > any room to expand memory-wise. Are there any options I can tweak to reduce > the memory footprint? Any other things I can disable that will cut down on > memory usage? Is Oak better in this regard? Thanks! > >
