lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Rutherglen (JIRA)" <>
Subject [jira] Commented: (LUCENE-753) Use NIO positional read to avoid synchronization in FSIndexInput
Date Mon, 30 Jun 2008 12:57:45 GMT


Jason Rutherglen commented on LUCENE-753:

Interesting results.  The question would be, what would the algorithm for allocating RandomAccessFiles
to which file look like?  When would a new file open, when would a file be closed?  If it
is based on usage would it be based on the rate of calls to readInternal?  This seems like
an OS filesystem topic that maybe there is some standard algorithm for.   How would the pool
avoid the same synchronization issue given the default small buffer size of 1024?  If there
are 30 threads executing searches, there will not be 30 RandomAccessFiles per file so there
is still contention over the limited number of RandomAccessFiles allocated.   

> Use NIO positional read to avoid synchronization in FSIndexInput
> ----------------------------------------------------------------
>                 Key: LUCENE-753
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: Store
>            Reporter: Yonik Seeley
>         Attachments:,,,,
FSIndexInput.patch, FSIndexInput.patch, lucene-753.patch
> As suggested by Doug, we could use NIO pread to avoid synchronization on the underlying
> This could mitigate any MT performance drop caused by reducing the number of files in
the index format.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message