On Wed, Jun 29, 2011 at 3:28 PM, Yonik Seeley <yo...@lucidimagination.com> wrote: > > On Wed, Jun 29, 2011 at 1:43 PM, Shawn Heisey <s...@elyograg.org> wrote: > > Just now, three of the six shards had documents deleted, and they took > > 29.07, 27.57, and 28.66 seconds to warm. The 1.4.1 counterpart to the 29.07 > > second one only took 4.78 seconds, and it did twice as many autowarm > > queries. > > Can you post the logs at the INFO level that covers the warming period?
OK, your filter queries have hundreds of terms in them (and that means hundreds of term lookups, which uses the term index). Thus, your termIndexInterval change is be the leading suspect for the slowdown. A termIndexInterval of 1024 means that a term lookup will seek to the closest 1024th term and then call next() until the desired term is found. Hence instead of calling next() an average of 64 times internally, it's now 512 times. Of course there is still a mystery about why your tii (which is the term index) would be so much bigger instead of smaller... -Yonik http://www.lucidimagination.com
