[ 
https://issues.apache.org/jira/browse/LUCENE-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612846#comment-13612846
 ] 

Michael Poindexter commented on LUCENE-4864:
--------------------------------------------

I figured out how to run the benchmark utility and ran a few tests on Windows.  
Results are not promising.  When I'm back I'll post the complete results here 
for posterity (I still want to run one or two more tests before then), but I 
think this issue can probably be closed as won't fix.
                
> Add AsyncFSDirectory to work around Windows issues with NIOFS (Lucene 5.0 
> only)
> -------------------------------------------------------------------------------
>
>                 Key: LUCENE-4864
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4864
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/store
>    Affects Versions: 5.0
>            Reporter: Michael Poindexter
>         Attachments: LUCENE-4864.patch, LUCENE-4864.patch
>
>
> On LUCENE-4848 a new directory implementation was proposed that uses 
> AsyncFileChannel to make a sync-less directory implementation (only needed 
> for IndexInput). The problem on Windows is that positional reads are 
> impossible without overlapping (async) I/O, so FileChannel in the JDK has to 
> syncronize all reads, because they consist of an atomic seek and atomic read.
> AsyncFSDirectoty would not have this issue, but has to take care of thread 
> management, because you need a separate thread to get notified when the read 
> is done. This involves overhead, but might still be better than the 
> synchronization.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to