Not much to go on with the cpu timings. Only 50% of the overall retrieval time is within retrieveDTable, and almost all of that is in preparing the sql/calling getString on the resultSet. We've gone as far as we can with this test case. The rough timings are down to 2.5 seconds for the page generation and it's not going to get much better.

Will now check for non-default sort and highlighting.

T
- posted by Tim Bruce @ 12:15 PM