how much more RAM consumption do you see when you force pooling?
pooling not forced -> memory after explicit GC: 50 MB
pooling forced -> memory after explicit GC: 250MB
Thank you for opening the JIRA issue.
Bogdan
>
> Mike
>
> On Fri, Mar 5, 2010 at 9:18 AM, Bogdan Ghidireac wr
Hi,
One of the use case of my application involves updating the index with
10 to 10k docs every few minutes. Because we maintain a PK for each
doc we have to use IndexWriter.updateDocument to be consistent.
The average time for an update when we commit every 10k docs is around
17ms (the IndexWrit
[
http://issues.apache.org/jira/browse/LUCENE-753?page=comments#action_12459971 ]
Bogdan Ghidireac commented on LUCENE-753:
-
The Javadoc says that transferTo can be more efficient because the OS can
transfer bytes directly from the
[
http://issues.apache.org/jira/browse/LUCENE-753?page=comments#action_12459868 ]
Bogdan Ghidireac commented on LUCENE-753:
-
You can find a NIO variation of IndexInput attached to this issue:
http://issues.apache.org/jira/browse/LUCENE
[ http://issues.apache.org/jira/browse/LUCENE-519?page=all ]
Bogdan Ghidireac updated LUCENE-519:
Attachment: NIOFSDirectory.java
> NIO FS implementation to avoid synchronization
> --
>
>
: Bogdan Ghidireac
Priority: Minor
Alternative implementation of FSDirectory that uses NIO to avoid sychronization
on the file pointer.
To use this, invoke Java with the System property
org.apache.lucene.FSDirectory.class set to
org.apache.lucene.store.NIOFSDirectory.
--
This message is
