This is interesting.
Very large heaps can sometimes cause an expensive gc cycle ("Can heap be
too big?" - http://www.javaperformancetuning.com/news/qotm045.shtml) and
different memory allocation patterns between 2.0 and 2.2 could I think play
in too, so it would be interesting to know the numbers
Hi,
I'm doing some Lucene search benchmarking (got to love massive query logs :))
and have 2 questions:
1) Has anyone compared Lucene 2.0 and 2.2-dev? My benchmarks found 2.2-dev
(freshly baked) to be somewhat slower than 2.0, despite all those performance
improvements (see CHANGES.txt)... Ha
