lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-2960) Allow (or bring back) the ability to setRAMBufferSizeMB on an open IndexWriter
Date Thu, 10 Mar 2011 20:42:59 GMT

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

Michael McCandless commented on LUCENE-2960:
--------------------------------------------

bq. IMO, this is such an obscure usecase that we shouldn't introduce any extra complexity
to implement it.

That this comes from Shay makes it not an "obscure" use case, IMO.

Ie, Shay (Elastic Search) is doing awesome things with Lucene, so if some change in Lucene
is adversely impacting Elastic Search, we should listen.

We already don't hear from Shay nearly as often as we should ;)

bq. For example, we should not guarantee exactly when a change to setRAMBufferSizeMB will
be seen... that could introduce the need for extra synchronization / memory barriers.

That's really an impl. detail.  Ie, what really matters is whether or not this change results
in any real change to index throughput.  If a volatile read per indexed doc (w/ rare volatile
write) really costs too much (unlikely) then we can make this "best effort".

> Allow (or bring back) the ability to setRAMBufferSizeMB on an open IndexWriter
> ------------------------------------------------------------------------------
>
>                 Key: LUCENE-2960
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2960
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Shay Banon
>            Priority: Blocker
>             Fix For: 3.1, 4.0
>
>
> In 3.1 the ability to setRAMBufferSizeMB is deprecated, and removed in trunk. It would
be great to be able to control that on a live IndexWriter. Other possible two methods that
would be great to bring back are setTermIndexInterval and setReaderTermsIndexDivisor. Most
of the other setters can actually be set on the MergePolicy itself, so no need for setters
for those (I think).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message