[
https://issues.apache.org/jira/browse/LUCENE-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624637#action_12624637
]
Michael McCandless commented on LUCENE-1329:
--------------------------------------------
bq. Mike, did someone measure what this brings?
I don't think so -- I haven't yet tested how much of a bottleneck this was /
how much it helps that isDeleted is no longer synchronized.
bq. This practically reduces need to have many IndexReader-s in MT setup when
Index is used in read only case.
I *really* want to get Lucene to this point, but I fear LUCENE-753 may still
stand in the way since many threads can pile up when accessing the same file.
Sadly, an optimized index exacerbates the situation (the polar opposite of what
you'd expect when optimizing an index). On every platform except Windows, this
patch combined with NIOFSDirectory ought to solve all known search-time
bottlenecks.
> Remove synchronization in SegmentReader.isDeleted
> -------------------------------------------------
>
> Key: LUCENE-1329
> URL: https://issues.apache.org/jira/browse/LUCENE-1329
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Affects Versions: 2.3.1
> Reporter: Jason Rutherglen
> Assignee: Michael McCandless
> Priority: Trivial
> Fix For: 2.4
>
> Attachments: LUCENE-1329.patch, LUCENE-1329.patch, lucene-1329.patch
>
>
> Removes SegmentReader.isDeleted synchronization by using a volatile
> deletedDocs variable on Java 1.5 platforms. On Java 1.4 platforms
> synchronization is limited to obtaining the deletedDocs reference.
--
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]
