Ok, added a couple of SQL tests using cursors with commits every 1000
records.

Also, a test where the real trigger program to use results data structures
for input/output to the shadow file. Originally used "legacy" i/o.

Test CPU used Clock Time
--------------------------------------------- ---------- ------------
file not journaled
update using RPGLE 25 1:00
update using SQL 24 :47
File journaled, no commitment control used
update using RPGLE 64 13:25
update using SQL 65 13:19
File journaled, using commitment control
update using RPGLE (single commit) 61 7:44
update using SQL (single commit) 61 4:47
update using RPGLE (commit every 1000 recs) 41 1:58
update using SQL Cursor (commit every 1000 recs) 78 2:22
File journaled, RPGLE commits every 1000 records
dummy RPGLE trigger, LR = *ON no files 260 7:30
dummy RPGLR trigger, LR = *ON 1 file 519 16:25
dummy RPGLE trigger, LR = *OFF no files 215 6:11
dummy RPGLE trigger, LR = *OFF 1 file 215 6:11
File journaled, RPGLE trigger updates "shadow" table
using SQL, no commit 470 34:52
using SQL, single commit 493 23:49
using RPG, commit every 1000 344 11:02
using SQL Cursor, commit every 1000 394 12:29
using RPG, commit every 1000, trigger using DS i/o 335 10:17

Personally, I expected a bigger difference by changing the trigger to use
results DS's for input/output to the file.

Maybe Barbara can comment.

Charles

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].