HP3000-L Archives

September 1998, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Scott McClellan <[log in to unmask]>
Reply To:
Scott McClellan <[log in to unmask]>
Date:
Wed, 16 Sep 1998 11:23:58 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Simonsen, Larry
> Sent: Wednesday, September 16, 1998 9:25 AM
> To: [log in to unmask]
> Subject:

> We have a site which does not have glancexl.  Is there a way
> of finding the process number of the memory manager.  So that by
> looking at two showproc listings one can estimate the load of the
> memory manager on a system?

The MPE/iX Memory manager is not implemented as a "process". Therefore
there is no process number associated with the memory manager. Memory
management code runs on all process stacks (and elsewhere). The memory
manager is insturments so that the measurement interface can collect
data on it. GlanceXl uses the measurement interface to display
information
about the memory manager. So do most other performance tools (I think).

In short, I can't think of any simple trick to figure out how much
memory
manager activity there is on a system without some performance tool.
One of the performance consultants on this list might have an idea,
however.

ATOM RSS1 RSS2