Re: Database I/O Modernization

It's not the CALL themselves that's the problem...

Can't tell for sure what it is without the code, but I'd suspect
- repeated opens
- ACTGRP(*NEW)
- data copying

Charles


On Mon, Sep 11, 2017 at 1:39 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Doesn't all these calls affect performance ?

I just ran a couple of benchmarks to compare the performance of reading all
the records of the CUSMSTF file.

Invoking the read op code within a do-while loop and checking for %eof() is
5.5 times more efficient than calling the CUSMSTIO procedure within a
do-while loop.

Yes, I would say that "all these calls affect performance" in a big
negative way.
--
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