Well then. We're running out of things to tune here; unfortunately 1.4 is still coming in at 2.28 secs versus 1.2's 1.55 second record.

The optimiser's showing that almost all objects created during the request handling are created within the Lucene framework, and the numbers aren't unreasonable. 14,828 "ScoreDoc" objects created is the biggie, and that corresponds to the 14,828 hits for our particular search. We probably can't prune that any lower without changing our approach (eg can we stop after 200?).

CPU time is also spent almost exclusively within Lucene. 91% of the time is within the Lucene search() call.

So we may be getting to the limits of tuning. I'm going to spend an hour or two going through the Lucene code to see if there are any obvious tweakables. Then tweak them.

T
- posted by Tim Bruce @ 2:51 PM