HP 3000 Manuals HP 3000 Manuals
Chapter 5 Performance Tuning
Proper performance tuning is important in keeping your system running as
efficiently as possible. Below we list some things you can do to ensure
optimum performance.
* Be sure your system has enough memory. MPE/V systems running
Access Server require a minimum of two megabytes. Four megabytes
or more are recommended in an HP OfficeShare networking
environment. MPE/XL systems running Access Server require a
minimum of 24 megabytes.
* On MPE/V systems, use the CONDENSE feature of VINIT regularly to
defragment discs. Performance in general suffers when free space
is spread across discs in small fragments. (This is not
applicable to Access Server running on MPE/XL.)
* With Access Server installed, you may need to use the :LIMIT
command to modify the maximum number of jobs and sessions allowed.
The primary DBA controls the maximum number of PC users allowed,
so the two of you might want to consult on this issue.
* Limit the amount of disc space available to each user, based on
individual data requirements. When Access Server is installed,
users are allowed unlimited space for saving result tables.
Setting limits helps control unnecessary space usage. The DBA can
use the Administrator Utility to set the maximum number of sectors
for each Access Server user.
* The default MPE priority queue for users is CS, but in configuring
users, the DBA can override the default and give users a DS or ES
priority for the HDSP. If speed is not essential for certain
users, placing them at a lower priority can improve performance
for other users on the system.
* You and the primary DBA should periodically review system
requirements and resource management. Be sure the tables set up
during implementation are appropriate for your system, and that
they continue to meet users' needs. Encourage users to keep their
own tables current and to delete those they no longer need.
* Allocate PCSERVER.PUB.SYS, HDSPNS.PPC.SYS, and HDSP.PPC.SYS before
starting Access Server on MPE/V. If Access Server is running on
MPE/XL, allocate only PCSERVER.PUB.SYS. MPE's :ALLOCATE command
allocates entries in the code segment table for each, and loads
the entries into the table. This speeds initial access to Access
Server for the first PC user logging on. Ensuring these programs
a slot in the code segment table also keeps them available for all
PC users logging on.
* Consider enabling disc caching on MPE/V, based on your system I/O
and CPU load pattern. (This is not applicable on Access Server
running on MPE/XL.)