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???
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
