 
| Subject: | |
| From: | |
| Reply To: | |
| Date: | Sat, 25 Feb 1995 20:41:15 GMT |
| Content-Type: | text/plain |
| Parts/Attachments: |
|
|
Goetz Neumann ([log in to unmask]) wrote:
: Adding one VTSERVER per session consumes about 2,000 sectors
: ( .5 MegaBytes) more transient space.
: Not much if you just move some users,
: but to consider, if you change it for a lot.
One reason that VTSERVER uses about 2,000 sectors of transient
space may be because it doesn't have a proper NMHEAP= or NMSTACK= value.
As a result, it inherits your system's default value. Then, when the VTSERVER
process is started, some portion of the NMHEAP and NMSTACK are allocated
on disk.
On my system, here's what one sample VTSERVER is using on disk:
Virtual Address Cur Size PID ObjCl #DskPgs
---------------- --------- ----- ----- -------
$00815.$40100000 $00100000 $01e7 $0046 16
$00815.$40200000 $01404030 $0000 $0049 16
$00815.$41605000 $00021000 $01e7 $0003 17
$00815.$41636000 $00200000 $01e7 $004d 16
$00815.$41836000 $00070000 $01e7 $0002 32
$00815.$419a6000 $04e20000 $01e7 $0053 0
$00815.$467c6000 $0000024c $0000 $00e3 1
$00815.$467c6280 $0000afc8 $0000 $00e3 11
$00815.$467d1280 $0000224c $0000 $004e 2
# disk pages occupied by listed objects: 111
(Information courtesy of (plug on) De-Frag/X (plug off))
The correlation between the Object Class number above and a
name for the Object Class is:
NM_STACK $02
CM_STACK $03
LDR_PROCESS_XRT $46
LDR_PFL table $49
USER_NM_DATA $4d
LDR_PLABEL table $4e
NM_HEAP $53
DCL_VTS_SVR $e3
Actually, VTSERVER is one of over 200 programs in @[log in to unmask] (about
196 in @.PUB.SYS alone) that have been improperly LINKed --> without
an NMHEAP or NMSTACK specification.
I first discussed (on the net) the lack of an NMHEAP specification for VTSERVER
in mid 1993, and dimly recall submitting a bug report to someone.
I also submitted a bug report to the VAB Prep group at HP in *1991* about
the lack of NMHEAP/NMSTACK, and again in 1993 & 1994.
Stan Sieler
[log in to unmask]
|
|
|
