RE: Size of Service Program

Well, as I recall, the issue as discussed in the past relates to the
ACTIVATION of the module(s) in service program. As always, when a
service program module gets activated, storage must get allocated and
initialized, which is costly. The whole idea of activation groups is to
all ONE startup cost (activation), with reuse of the already activated
code as needed. If you do something silly, like making your service
program module start ACTGRP(*NEW), your huge service program could be a
performance nightmare.

Where, I'm a little fuzzy is whether all modules in a particular service
program are activated at the same time. We only use single-module
service programs here, so I haven't had to deal with this yet.

Hth,
-Eric DeLong

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Monday, November 08, 2010 10:45 AM
To: RPG programming on the IBM i / System i
Subject: Re: Size of Service Program

What kind of performance metric are you interested in? Service program
load
performance? Runtime call performance? Both? Memory use? How can
memory use
affect overall system performance? I don't want to imply that I know
the answer
to these questions, but I'm interested in hearing other's responses, so
I hope
it helps to break out different performance metrics.

-Nathan



----- Original Message ----
From: Robert Mullis <robertmullis99@xxxxxxxxxxx>
To: RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
Sent: Mon, November 8, 2010 9:25:29 AM
Subject: Size of Service Program

My source is divided by applications, A/P, POS, etc. Within each
application, there is a service program with all the reusable procedures

for that application. Recently when adding new procedures to the
service program in a particular application, I noticed that this service

program was getting large, object size and also the number of procedures

it contained. I have never read anywhere that the larger the size of a
service program became, the poorer it performed. Is there a theoretical

size limit when a service program's performance becomes affected?