|
On Wed, 2005-12-14 at 16:05 -0600, Scott Klement wrote: > > Therefore, I wrote two programs to test this: > > > > read_test > > http://code.midrange.com/index.php?id=43c4fd6a02 > > Try changing READ_TEST to specify BLOCK(*YES) on the F-spec. > > > > reade_test > > http://code.midrange.com/index.php?id=e3203a5c0b > > (Note that if you specify BLOCK(*YES) on the F-spec for READE_TEST it'll > give you a RNF7092 (severity 10) error in the compile listing. Look at the > text of that message for details) > > Does this change your benchmark scores appreciably? Yes, on average, READ gets worse. The average for READ in the latest tests was 17 secs, and the READE average improved slightly to 15.8 secs. However, if I throw out the best and worst for both, READ has a bit of an advantage, 14 secs vs 16 secs or about 12.5 %. So, _if_ block(*yes) is specified (and doesn't RNF7092 because of other parts of the code) _and_ reade is changed to read with a condition, you may see some benefit, or maybe not, I suppose depending on how organized the file is. But certainly not to the level of 'READE is a dog! Change it to READ + condition for a big performance boost'. Regards, Rich
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.