lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vitaly Funstein <>
Subject Direct memory footprint of NIOFSDirectory
Date Tue, 10 Jul 2012 02:59:37 GMT

I have recently run into the situation when there was not a sufficient
amount of direct memory available for IndexWriter to work. This was
essentially caused by the embedding application making heavy use of JVM's
direct memory buffers and not leaving enough headroom for NIOFSDirectory to
operate. So what are the approximate guidelines, if any, in terms of JVM
configuration for this choice of Directory to operate safely? Basically,
what I am looking for is a rough estimate of direct memory usage per GB of
indexed data, or per directory/writer instance, if applicable.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message