[
https://issues.apache.org/jira/browse/LUCENE-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624657#action_12624657
]
Eks Dev commented on LUCENE-1329:
---------------------------------
ok, I see, thanks.
At least, It resolves an issue completely for RAM based indexes.
We have seen performance drop for RAM based index when we switched to MT setup
with shared IndexReader, I am not yet sure what is the reason for it, problems
in our code or this is indeed related to lucene. I am talking about 25-30% drop
on 3 Threads on 4-Core CPU. Must measure it properly...
> 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]
