It's been a while since I've managed a system running GrowthPower, so take
these suggestions with a grain of salt...

First, try OCTCOMPing the programs. Works wonders on our SPL programs here.
Don't forget to OCTCOMP the SL, also. May not work with your situation, but
worth a try...

Second, do you need to use the terminal timeout feature? And does *not*
using it ease your CPU utilization?

Third, see if you can get the user base to push for some native-mode code.
If Pivotpoint still considers GrowthPower a viable product (and I assume
they do if they've come out with GP2000), they should at least consider
this. (How long have HP-PA machines been on the market??)

Good luck,

--
Paul S. Butler
System Administrator, Smart Title Solutions

Phone 916 797-5000 ext. 5004
Fax 916 797-5001


"Bob Rose" <[log in to unmask]> wrote in message
news:F4B1826B1A21D211AEC5006008207AF404377FBB@dogbert.csillc.com...
I work at a medium sized manufacturing company that has been using
Growthpower
since 1985.  We upgraded from Growthpower 11.0 to Growthpower 2000 last
October
and have been experiencing significant performance problems ever since.

<snip>

Growthpower runs in CM, and none of the programs are
OCTCOMP'd.  We're using SOS to monitor system utilization.  Prior to this
upgrade, we would see the system running at around 70%.  Now, it's usually
in
excess of 95%.

We've seen this problem before, when we upgraded from 9.0 to 11.0.

 <snip>