Rick writes:
> What I have suggested is that we should really look at switching our
> programs from CM to NM. There is a tremendous amount of overhead due to
> this. Another area I think we should be looking at is the databases.
> Maybe a good 'tweaking' or a reorganization is what they need. The
> biggest problem is time....

Ahh...CM?!  I have seen a COBOL sudden performance problem
before, having to do with arithmetic overflow (during word->byte address
calculations) getting silently (and correctly, if expensively) handled
by CM COBOL runtime.  Perhaps someone who remembers more may comment.

Absent that, I'd like to know: when performance is "bad", what's the
CPU utilitization?  A cheap/easy way is to check the free CPU
speedometer on every HP 3000:
http://www.allegro.com/papers/dump.html#Speedometer

If you're at, say, 75% or more CPU use, more memory isn't likely to help.


--
Stan Sieler                                          [log in to unmask]
P.s.: please forgive typos/brevity,      http://www.allegro.com/sieler/
      I'm typing left-handed for awhile.