|
> If so, could you add BLOCK(*YES) to the F-spec > for the READ version, and retest? It is my > contention that the performance boost will > flabbergast you. Thank you for the tip. It was relevant to a procedure I just wrote which sometimes scans hundreds of records. I added Block(*Yes) to the F spec, which dropped the job's I/O count to aproximately 1/10, and dropped the CPU consumption to 1/3 of the previous use. Without blocking an SQL alternative was faster, but with blocking the native I/O is fastest. Thanks, Nathan.
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.