[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vmsdev::vmstuning

Title:VMSTUNING
Notice:Welcome to VMSTUNING
Moderator:EVMS::HALLYB
Created:Sat Feb 15 1986
Last Modified:Wed May 14 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1539
Total number of notes:7984

1529.0. "overhead of increased sysuaf params ?" by FIREBL::LEEDS (From VAXinated to Alphaholic) Thu Jan 23 1997 10:28

T.RTitleUserPersonal
Name
DateLines
1529.1LAIDBK::PETERSON_RIRick PetersonFri Jan 24 1997 03:3418
    the *lm hae no immediate impact as they are limits.  They only really
    come into paly as applications actually use them and subsequently start
    allocating the space - usually in NPAGEDYN for each used - limited
    ultimately by bytlm.
    
    the WS* parameters can be troublesome as process headers are presized
    to taking into consideration procsectcnt, WSMAX, and virtualpagecnt.
    Also, if WSQUOTAs get consistently very large and there is a memory
    shortage, some thrashing can occur.
    
    ACP_WINDOW is another one.  It is best to use set vol or init to
    initalize a volume that will have that level of fragmentation.  Setting
    the parameter that large wastes space for all disks...
    
    The IDSM and the File System Internals books are good sources of
    info...
    
    Peace,  Rick