[
https://issues.apache.org/jira/browse/LUCENE-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625051#action_12625051
]
Yonik Seeley commented on LUCENE-753:
-------------------------------------
bq. Maybe we can do this in time for 2.4?
+1
Latest patch is looking good to me!
Is there a reason we don't do lazy allocation in clone() like FSIndexInput?
Also, our finalizers aren't technically thread safe which could lead to a
double close in the finalizer (although I doubt if this particular case would
ever happen). If we need to keep them, we could change Descriptor.isOpen to
volatile and there should be pretty much no cost since it's only checked in
close().
> Use NIO positional read to avoid synchronization in FSIndexInput
> ----------------------------------------------------------------
>
> Key: LUCENE-753
> URL: https://issues.apache.org/jira/browse/LUCENE-753
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Store
> Reporter: Yonik Seeley
> Assignee: Michael McCandless
> Fix For: 2.4
>
> Attachments: FileReadTest.java, FileReadTest.java, FileReadTest.java,
> FileReadTest.java, FileReadTest.java, FileReadTest.java, FileReadTest.java,
> FSDirectoryPool.patch, FSIndexInput.patch, FSIndexInput.patch,
> LUCENE-753.patch, lucene-753.patch, lucene-753.patch
>
>
> As suggested by Doug, we could use NIO pread to avoid synchronization on the
> underlying file.
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
