|
In the "General performance considerations" chapter of the redbook Striving
for Optimal Journal Performance on DB2 Universal Database for iSeries
(SG24-6286-00), it has the following recommendation:
"Specify Sequential Only on OVRDBF
Where possible, use the CL command OVRDBF to specify sequential-only
processing when adding rows to your database tables. Also, consider using
separate open data paths (ODPs) and open these for output when adding large
amounts of rows to your database tables.
Also, specify the NBRRCDS parameter with a value as close to
128KB/row-width as possible to maximize memory buffer utilization."
I have tested this, especially since we turned on journaling and
performance on this one application that writes 20M records to a table, and
found a signficant boost in performance. But I note that this redbook was
written 15 years ago and mentions in the edition notes that "This edition
applies to Version 5 Release 1 of OS/400". Can anyone advise whether this
particular recommendation, specifically WRT the 128KB/row-width, still
applies today? (We're on Power 8, v7r1.) If I go with a bigger block than
128KB, at what point do I need to be concerned with resource contention?
- Dan
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.