I did a test and it is still pretty easy to reverse merge the original
performance patch to get things back to the way they were when you first
got things working. Do you think it would be easier for you if we go back
to that point and you just try the performance patches again from square
one? I would suggest going right to the areas where you think you got the
biggest performance gains and skipping the smaller changes that didn't
make much difference. If nothing else, we should try to take them one at
a time so we know which specific change caused the breakage.
I didn't back it out yet because I want to hear your thoughts. I
absolutely do not mind continuing the way we have been until we get it all
working again. It just seems like we might have changed too many things
in that one commit and we perhaps should redo it in smaller pieces. That
way, if you want get rid of an inner loop we can look at that change in
isollation. Even if they are not big performance gains, better code is
better code. Since testing is hard we should probably just do them one at
a time.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Fri Jul 1 11:17:45 2005