Improving table checkpoint performance

I would be willing to bet that a large part of that 15-20 seconds of the check point is not the actual checking but the object recognition.  You're passing an Aliased object to the check point, if it's not been accessed before in the test, it's not in cache so TestComplete needs to get the object and then pass it into the check point.  If there are delays in having the grid display on screen, the project has an auto-wait time out that defaults to 10 seconds so there will be, at most, 10 seconds simply for object recognition.

So, the best bet here is to see what you can do about tweaking performance in object recognition.  Look to see if there are "extended find" calls in the object mapping tree and, if so, consider mapping more parent components to speed up this process.

I think, generally, you're dealing with the overhead of object recognition.  The best bet beyond that is to not use check points that grab whole tables but make your test more targetted... you changed a piece of data, you know it will add a row to the grid.  Compare the row count before to the row count after.  If it increases, you've verified at least part of the test.  Next, grab the data from the row.  Compare it to what you entered in earlier in the test.  If it matches, you're golden.  No need to compare the whole table if all you need to check is a row or cell or so on.