VMS Help  —  SHOW  MEMORY  Examples
Shows the use of dynamic memory areas consisting of variably sized blocks. 1 Current Size Current size (in 512-byte pagelets on Alpha ) of each dynamic memory area. For the lock manager display, the unit of measurement is megabytes. 2 Initial Size Initial size of nonpaged dynamic memory and the name of the system parameter (NPAGEDYN) that controls this size. 3 Maximum Size Maximum size to which nonpaged dynamic memory can grow and the name of the system parameter (NPAGEVIR) that controls this size. 4 Free Space Amount of free space in each dynamic memory area. 5 Space in Use Amount of space currently allocated from each area. 6 Largest Block Size of the largest contiguous area in each pool area. 7 Smallest Block Size of the smallest hole (free block) in each pool area. 8 Free Blocks Total number of free blocks in each pool area. The size of this number is a measure of pool fragmentation. 9 Blocks LEQU 64 Number of free blocks that are 64 bytes long or shorter. This number is another measure of pool fragmentation because while allocation of these small blocks is unlikely, they contribute to the allocation time whenever an allocation request is made. 10 Empty Pages Number of pages that do not have any packets allocated. 11 Free Packets Total number of packets not in use. This number is the sum of free packets from partially used pages and the packets of all Empty Pages. 12 Hits Total number of packet allocations. 13 Misses Total number of packet allocation requests that could not be satisfied because the number of packets requested were not available. A miss causes dynamic memory to expand by one page to satisfy the packet allocation request. 14 Expansions Total number of times that dynamic memory increased by a page to satisfy packet allocation requests. 15 Packet Size Packet size of 256 bytes, which is used by the lock manager to hold either a lock block data structure or a resource block data structure. 16 Lookasides Total number of memory packets placed Free Blocks on "lookaside lists". If a packet of the correct size is on a lookaside list, it can be allocated very quickly and efficiently, however, it cannot then be used as part of any other size packet. An excess of packets on the lookaside list can be a cause for the inability to allocate other sizes. 17 Over-limit Total number of memory packets that exist Lookaside Blocks on "lookaside lists" that are no longer actively used because the SYSGEN parameter PAGED_LAL_SIZE was lowered. These packets will be available for use again if the SYSGEN parameter is increased to include them, or if there was a paged pool shortage and they are reclaimed. If there are no lookaside list packets on these "over-limit" lists then this line will not appear. 11. $ SHOW MEMORY/FILES System Memory Resources on 22-MAY-2001 19:04:19.67 Swap File Usage (8KB pages): Index 1 Free Size DISK$ALPHASYS:[SYS48.SYSEXE]SWAPFILE.SYS 1 904 904 DISK$SWAP:[SYS48.SYSEXE]SWAPFILE.SYS;1 2 1048 1048 Total size of all swap files: 1952 Paging File Usage (8KB pages): Index 2 Free Size DISK$PAGE:[SYS48.SYSEXE]PAGEFILE.SYS;1 253 16888 16888 DISK$ALPHASYS:[SYS48.SYSEXE]PAGEFILE.SYS 254 16888 16888 Total size of all paging files: 33776 Total committed paging file usage: 3 1964 Paging File Usage (in blocks) Shows the usage of paging and swapping files. 1 Swap File Usage Number of swap files. Begins with an index value of 1 and increases in count. 2 Paging File Number of page files. Begins with an index Usage value of 254 and decreases in count. 3 Total Paging Total committed page file usage. As in File Usage previous releases, more pages can reside in page-file sections systemwide than would fit into installed page files.
Close Help