Adrein, I have created an index of size 370M of 1 million docs of 40 fields of 40 chars and did the profiling. I see that the indexing and in particular the addDocument & ConcurrentMergeScheduler in 4.1 takes double the time compared to 3.0.2.
Looks like CompressionStoredFieldsFormat is of little use in my scenario. Arun On Tue, Jan 29, 2013 at 8:35 PM, Adrien Grand <jpou...@gmail.com> wrote: > Arun, > > Lucene uses a very light compression algorithm so I'm a little > surprised it can make indexing 2x slower. Could you run indexing under > a profiler to make sure it really is what makes indexing slower? > > Thanks! > > -- > Adrien > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
