You can also set the termsIndexDivisor when opening the IndexReader. The terms index is an in-memory data structure and it an consume ALOT of RAM when your index has many unique terms.
Flex (only on Lucene's trunk / next major release (4.0)) has reduced this RAM usage (as well as the RAM required when sorting by string field with mostly ascii content) substantially -- see http://chbits.blogspot.com/2010/07/lucenes-ram-usage-for-searching.html Mike On Tue, Jul 13, 2010 at 6:09 PM, Paul Libbrecht <p...@activemath.org> wrote: > > > Le 13-juil.-10 à 23:49, Christopher Condit a écrit : > >> * are there performance optimizations that I haven't thought of? > > The first and most important one I'd think of is get rid of NFS. > You can happily do a local copy which might, even for 10 Gb take less than > 30 seconds at server start. > > paul > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
