[
https://issues.apache.org/jira/browse/LUCENE-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099195#comment-13099195
]
Simon Willnauer commented on LUCENE-3416:
-----------------------------------------
bq. Reading a volatile var in x86 is not a cache invalidation, though it does
come with a cost.
yes unless you are reading and writing it. Yet since this is not intended here
we don't need to get into details. Bottom line that synchronization doesn't
make much sense here. we should try to control some order here that we can not
control. if somebody sets either of those concurrently they should take care of
synchronization. What should I expect if you set this concurrently? IMO we
should craft those method to work without synchronization which is certainly
possible. synchronized here buys us nothing and should be removed.
> Allow to pass an instance of RateLimiter to FSDirectory allowing to rate
> limit merge IO across several directories / instances
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3416
> URL: https://issues.apache.org/jira/browse/LUCENE-3416
> Project: Lucene - Java
> Issue Type: Improvement
> Components: core/store
> Reporter: Shay Banon
> Assignee: Simon Willnauer
> Attachments: LUCENE-3416.patch
>
>
> This can come in handy when running several Lucene indices in the same VM,
> and wishing to rate limit merge across all of them.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
