Subject: | |
From: | |
Reply To: | |
Date: | Mon, 8 Jan 2001 11:07:50 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Dave gets miffed:
> At first I was miffed at your need-to-know-basis response, but after
> reviewing the documentation, it is clear why you responded as you
> did, that is, it is highly dangerous ;-|
The longer answer is that marking something resident is likely to be just
one of a list of similarly obscure and arcane things that you need to do in
order to solve any problem whose solution involves resident code (such as
intercepting an interrupt, patching resident NL code, etc.), so it's
unlikely that someone asking how to make something resident knows all these
other things but not this one particular thing.
It's much more likely that they think they know more than MPE does and want
to override MPE's idea of what should be in memory by playing with making
application programs resident, etc. :-)
MPE does an excellent job of managing its resources and such tweaks rarely
(if ever) result in performance improvements. A significant percentage of
performance consulting cases we're involved with end up resulting in the
only significant change required being a return to the default HP
configuration for things like :TUNE parameters, after which the machine
starts running much better :-)
G.
|
|
|