On Fri, Nov 20, 2015 at 8:02 PM, Roll, Kevin <[email protected]> wrote: > I commented out Lucene in my repository.xml but this has now broken our > system ("no search manager configured for this workspace"). Glancing at the > code I do not see any other subclasses of AbstractQueryHandler. What are my > options here? We cannot afford to keep an entire Lucene index in memory as it > is consuming too much. We don't do any queries more complicated than "where > [jcr:mimeType] like 'image%%'", so I really feel like Lucene is overkill. Do > I have an alternative? Thanks.
That looks like a question better suited for the Jackrabbit user's list. At any rate, IIRC, Jackrabbit's indexes include everything by default, while Oak's do not - they have to be explicitly configured. That being said, I'm not sure how Oak compares to Jackrabbit when you want to optimise memory consumption. Robert > > From: Roll, Kevin > Sent: Thursday, November 19, 2015 8:46 AM > To: '[email protected]' > Subject: Memory usage > > We have encountered OutOfMemoryErrors on our Sling server under heavy usage. > Unfortunately we need to run on old 32-bit hardware in the field that does > not have a lot of memory. I am disabling Lucene because our app is focused on > images, not text, and Lucene seems to consume a lot of memory. Are there any > other things I should consider that would make a substantial difference in > Sling's memory consumption? Bundles I could remove, settings I could tweak, > etc? Thanks! >
