Mark Gross ([log in to unmask]) wrote:
: I updated MPE/ix from 5.0 to 5.5 pp4 over the weekend. The process went
: fairly well and took about 6 hours. I was a bit displeased, however, to see
: my batch jobs taking up to 42% longer to complete, with the average being
: about 30%. YIKES! I expected to take a performance hit, but is this normal?
: We are running a 937LX with 128Meg of memory.

No, it is NOT Normal.  There are several possible causes of a general
performance slowdown that you might check for on your system.

1. Disc space use and allocation may have changed. If your discs were
fragmented by the upgrade or your free space has all wound up on one drive or
all the new files went to the same drive, you will have a problem.
Check your disc usage and access rates via Glance/iX or other performance
tool.
Do a DISCFREE A, b and c.  Defrag your disks.  Maybe even RELOAD if possible.

2. Verify that the SL is still OCT'ed.  The SL.PUB.SYS should be large
(EOF over 40000 I think, Ours is 125000 records).

3. If only specific jobs are slower, check out what they are doing.  Do
they use more CPU or just elasped time??  Are they KSAM oriented??  Image?
Allbase?  etc.

4. Check your UDC's.  I've seen cases where UDC files have been appended
such that the same UDC file was searched many times for each command.
Also, cases where important UDC's (System wide file equates, etc.) were lost.

5. Check for CM program allocation (We do ours in a JOB started from the
SYSSTART file).
Check that any OCT'd programs were not upgraded (FOS or third party).
Had you "switched" QUERY.PUB.SYS for the NM version for example??

6. Had you customized your job queue priorities?? Perhaps by shortening
the quantum??  Do a SHOWQ;STATUS to check the queue defintions.


Hope these ideas help.  Generally My testing has found that each version
of the OS is a bit faster than the old, once such disc and other factors
are eliminated.  (I do some performance testing of my products as a sanity
check). Of course, these factors are mostly for Jobs, while large numbers
of sessions may experience the "knee" problem, or the "out of memory causes
swapping" problem, that does not seem to be your problem.

--
 James Overman HP Support Technology Lab  Roseville, CA