Hmmm, since 4.1, fields have been stored compressed by default. I suppose it's possible that this is a result of compressing/uncompressing.
What happens if 1> you enable lazy field loading 2> don't load any fields? FWIW, Erick On Thu, Sep 26, 2013 at 10:55 AM, Desidero <desid...@gmail.com> wrote: > A quick update: > > In order to confirm that none of the standard migration changes had a > negative effect on performance, I ported my Lucene 4.x version back to > Lucene 3.6.2 and kept the newer API rather than using the custom > ParallelMultiSearcher and other deprecated methods/classes. > > Performance in 3.6.2 is even faster than before (~2900 requests/min with 4.x > vs ~6200 requests/min with 3.6.2), so none of my code changes should be > causing the difference. It seems to be something Lucene is doing under the > covers. > > Again, if there's any other information if I can provide to help determine > what's going on, please let me know. > > Thanks, > Matt > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
