[ https://issues.apache.org/jira/browse/LUCENE-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Rutherglen closed LUCENE-2063. ------------------------------------ Resolution: Won't Fix Sorry if this spam's things, however it's unlikely that I'll work on these. > 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: 4.0 > > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org