Re: Using NoOpMergePolicy (Lucene 2331) from Solr
Jason Rutherglen wrote: Tom, Interesting, can you post your findings after you've found them? :) Jason On Tue, Apr 27, 2010 at 2:33 PM, Burton-West, Tom tburt...@umich.edu wrote: Is it possible to use the NoOpMergePolicy ( https://issues.apache.org/jira/browse/LUCENE-2331 ) from Solr? We have very large indexes and always optimize, so we are thinking about using a very large ramBufferSizeMB and a NoOpMergePolicy and then running an optimize to avoid extra disk reads and writes. Tom Burton-West I've never tried it but NoMergePolicy and NoMergeScheduler can be specified in solrconfig.xml: ramBufferSizeMB1000/ramBufferSizeMB mergePolicy class=org.apache.lucene.index.NoMergePolicy/ mergeScheduler class=org.apache.lucene.index.NoMergeScheduler/ Koji -- http://www.rondhuit.com/en/
RE: Using NoOpMergePolicy (Lucene 2331) from Solr
Thanks Koji, That was the information I was looking for. I'll be sure to post the test results to the list. It may be a few weeks before we can schedule the tests for our test server. Tom I've never tried it but NoMergePolicy and NoMergeScheduler can be specified in solrconfig.xml: ramBufferSizeMB1000/ramBufferSizeMB mergePolicy class=org.apache.lucene.index.NoMergePolicy/ mergeScheduler class=org.apache.lucene.index.NoMergeScheduler/ Koji -- http://www.rondhuit.com/en/
Using NoOpMergePolicy (Lucene 2331) from Solr
Is it possible to use the NoOpMergePolicy ( https://issues.apache.org/jira/browse/LUCENE-2331 ) from Solr? We have very large indexes and always optimize, so we are thinking about using a very large ramBufferSizeMB and a NoOpMergePolicy and then running an optimize to avoid extra disk reads and writes. Tom Burton-West
Re: Using NoOpMergePolicy (Lucene 2331) from Solr
Tom, Interesting, can you post your findings after you've found them? :) Jason On Tue, Apr 27, 2010 at 2:33 PM, Burton-West, Tom tburt...@umich.edu wrote: Is it possible to use the NoOpMergePolicy ( https://issues.apache.org/jira/browse/LUCENE-2331 ) from Solr? We have very large indexes and always optimize, so we are thinking about using a very large ramBufferSizeMB and a NoOpMergePolicy and then running an optimize to avoid extra disk reads and writes. Tom Burton-West