|
Bob, Bob Larkin wrote: > John, > Great work. Now for some real fun, have your program open a file, read a >record, then > return. After that, try leaving LR *OFF. Because we were testing to see whether there was a performance difference between qualified and unqualified calls, the program was written so that it would do the least amount of work.... thereby minimizing other complicating inputs to the results. The *INLR *ON approach was selected in order to ensure that the extra perfromance penalty of re-opening (and resolving authority to) the program _was_ incurred each time. The excercise was to measure the cost of qualifying a program call, so I tried to design the test to isolate (as much as possible) that event. > The only reason I mention that is that there can be great savings there. I >ran into a > situation where program A was calling Program "Tax Calc" several times for >each > transaction. The transactions were telephone calls, so there were many >millions per > cycle. A minor change to keep the "Tax Calc" from closing the files and >going away > resulted in a reduction from 11 HOURS to 17 Minutes!!! I don't doubt it. Leaving the program and the files open in that situation is the right thing to do, and bound to return better performance results. Hopefully nobody is using my little test program as an example of the right way to code! :~) jte -- John Earl johnearl@400security.com The PowerTech Group 206-575-0711 PowerLock Network Security www.400security.com -- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.