I too have read that Journaling with commitment control is almost as
fast as no journaling at all..
Now, it is important for us to journal, first for tracking problems, and
second for DR.
We don't currently have commitment control in our programs.
We have some batch programs, that perform tens of thousands of journaled
updates. These programs are what are killing the IO... Would it be as
"simple" as adding a "strcmtctl" before my call, and a "commit" after it?
I may have the mistaken impression that commitment control was to
protect at a transactional level, not to use it at a mass file update
level???
