[
https://issues.apache.org/jira/browse/LUCENE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777666#action_12777666
]
Jason Rutherglen commented on LUCENE-2063:
------------------------------------------
Right, this isn't the highest priority, however try running the
LUCENE-1313 and you'll see a lot of unique thread objects being
created because of the small segment merges happening quickly on
the RAMDir.
It can also potentially be used for LUCENE-2047, or a follow on
async patch.
> Use thread pool in ConcurrentMergeScheduler
> -------------------------------------------
>
> Key: LUCENE-2063
> URL: https://issues.apache.org/jira/browse/LUCENE-2063
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Affects Versions: 2.9.1
> Reporter: Jason Rutherglen
> Priority: Minor
> Fix For: 3.1
>
>
> Currently it looks like CMS creates a new thread object for each
> merge, which may not be expensive anymore on Java5+ JVMs,
> however we can fairly simply implement the Java5 thread pooling.
> Also I'm thinking we may be interested in using thread pools for
> other tasks in IndexWriter (such as LUCENE-2047 performing
> deletes in the background).
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
