|
On Tue, 11 Mar 2003, Buck Calabro wrote: >> The number one problem will be run time performance. >>Creating a new AG is roughly equivalent to starting >>a new job. Scott said: >This is not even remotely true.... The time it takes >to create an activation group is a tiny fraction of >the time it takes to create a job. > >Here are my benchmarks on activation group performance: >http://archive.midrange.com/rpg400-l/200208/msg00397.html Hi Scott! Once again I opened my yap and made it worse. Your benchmarks use very little storage. That is, the called program doesn't have to initialise anything. In a more typical RPG environment, there are files to be opened, variables to initialise and so forth. My original comment was based on practical experience with large-ish RPG programs in the CISC days. Looking at your numbers (again!) makes me realise I should probably build some test jigs and get more modern numbers before I muddle the issue more. I have no *NEW programs that I can quickly run tests on. --buck
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.