Tried changing the merge policy but it had no effect on the test
times. But I can rule out ReiserFS as the culprit now too, since I was
able to run with indexes stored on an ext3 partition, and observed a
similar slowdown.
So there's something else going on here with this particular test
setup, bu
one major thing that changed from 3.0.3 to 3.5 is that we use
TieredMergePolicy by default. can you try to use the same merge policy
on both 3.0.3 and 3.5 and report back? ie LogByteSizeMergePolicy or
whatever you are using...
simon
On Thu, Feb 9, 2012 at 5:28 AM, Vitaly Funstein wrote:
> Hello,