Journal caching is quite helpful performance wise in an environment
- that has lots of "batch" processing, with lots of records updated
- in which the tables are journaled and commitment control is rarely if
So while such an environment is often the result of turning on journally
for some HA product, it doesn't have to be.
I believe it was Rob Berendt @ Dekko who found the performance improvement
from turning on journal caching was much, much greater than the one he got
from moving from spinning disks to SSDs.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.