The second part of the STATS RESOURCE display shows how system memory is used. The STATS RESOURCE display and the STATS USER SIZE histogram are used to set the resource memory util ization tuning parameters.
ST A TS RESOURCE Display for Memory Utmzation
In the following example of a STATS RESOURCE display of memory utilization, note the zero-valued items. Zero-value items are normally suppressed. They are included here to acquaint the reader with these possible display items.
CES0-00 STATS RESOURCE Display for Memory Utilization Modu I e 6-3
147
STATS interval from 08:08:36.94 to 15:39:12.98 CP-6 memory utilization
AARDVARK and RECOVERY 45
XDELTA and monitor debug schema 112 Monitor procedure and static data 259 Monitor context (JITs, HJITs, PPUT, page tables) 47
Monitor dynamic data segments 27
TIGR-bui It tables 50
Communications WSQs 30
Comgroup queue 51
Total pages held back for monitor use 15
Resident system ghosts 384
Required processors (IBEX, DELTA, LOGON) 228 AI I other special shared (resident) processors 599
Total dedicated memory 1847
Avai lable to users 6345
Currently 01 located to users 1620
Automatically shared run units in use 394
Shared data segments in use 10
Free pages 99
Automatically shared run units not in use 685 I/O cache pages (Use Count - 0) 3402 Total pages currently avai lable 4201
Suspected bad physical pages 0
Physical pages being tested 0
Confirmed bad physical pages 0
I/O cache pages 3529
Number of pages not accounted for 8 Total physical pages in system 8192
Figure 16. STATS RESOURCE Display of Memory Utilization
The items in this part of the STATS RESOURCE display are described in the following table. For a GLOM data reduction, this part of the RESOURCE display will show the average memory usage for various system functions. During operation, the total dedicated memory remains constant. The remaining memory categories are changing very
rapidly.
148 STATS RESOURCE Display for Memory Utilization Module 6-3
CE68-0e
Table 10. STATS RESOURCE Memory Display Definitions
Item Definition
AARDVARK and RECOVERY
Pages required for the boot processor (AARDVARK) and the automatic recovery processor (RECOVERY).
XDELTA and monitor debug schema
Pages required for the monitor debugger (XDELTA) and the debug schema used to debug the monitor. The size of the debug schema area may change by specifying different values to the FUNCTIONAL CODE GROUPS question at boot time.
Monitor procedure and static data
Pages required for the monitor executable procedure (i.e .•
PROC:X ... ) and static data (i.e .• DCLX ... XSTATIC).
Monitor context (JITs. HJITs. PPUT. page tables)
Pages required for the monitor context area. which includes the monitor Job Information Table (JIT). House-keeping JIT (HJIT). physical page use table (PPUT). and page tables (PT).
Monitor dynamic data segments
TIGR-built tables
Communications WSQs
Comgroup queue
CE60-00
Pages required for monitor dynamic segments. which includes CFUs. LOCTs. ASAVE and ENQ.
Pages required for tables built by TIGR at boot time. This includes the user table. I/O cache. device tables and autoshare tables.
Pages used in communication with FEPs. These pages are control led by the INQSZ and OUTQSZ parameters on the TIGR processor FEP command.
An area for comgroup context.
STATS RESOURCE Display for Memory Utilization Module 6-3
149
Table 10. STATS RESOURCE Memory Display Definitions (cont.)
Item Definition
Total pages held back for monitor use
Resident system ghosts
Pages reserved for CFUs, LOCTs, ASAVE, ENO and stealable pages. These pages are affected by the CFU, DEVMAX, ENO, and STEALPGS options on the TIGR processor MaN command.
Pages required for resident system ghosts. These are ghost users that perform part of the operating system's functions such as ELF, PIG, SLUG, INSYM, and CUTSYM (and are referred to as the MING ghosts).
Required processors (IBEX, DELTA, LOGON)
Pages required for the IBEX, DELTA, and LOGON processors.
These processors must be present for the system to function.
AI I other special shared (resident) processors
Pages required for 01 I processors, shared libraries,
alternate shared libraries, and debuggers. These items are specified on the SPROC options on the TIGR processor MaN command.
Total dedicated memory
Available to users
Total pages required by the monitor, its tables, ghosts, and processors.
Pages available to users. This number is the difference between the total pages in the system and the total dedicated memory.
Currently allocated to users
150
Pages that are currently actually allocated to users.
These pages cannot be shared. These pages plus the
automatically shared run unit pages in use, plus the shared data segments in use constitute all user memory.
STATS RESOURCE Display for Memory Utilization Module 6-3
CE60-00
Table 10. STATS RESOURCE Memory Display Definitions (cont.)
Item Definition
Automatically shared run units in use
Pages of procedure of automatically shared run units that are currently being used by one or more users.
Shared data segments in use
Free pages
Pages of shared data segments currently being used by one or more users.
Pages in the system not currently used for any purpose.
Automatically shared run units not in use
Pages of the procedure of automatically shared run units that are not being used by any user. The pages are
candidates to be used for other purposes if the free pages are exhausted.
I/O cache pages (Use Count-0)
I/O cache pages not currently being used.
Total pages currently available
Pages on the system that are currently avai lable for use.
This number is the sum of the free pages and pages for the automatically shared run units not in use.
Suspected bad physical pages
Pages that have been marked as suspect by TOLTS.
Physical pages being tested
Pages that are currently being tested by TOLTS.
Confirmed bad physical pages
CE60-00
Pages that have been partitioned by SYSCON.
STATS RESOURCE Display for Memory Utilization Module 6-3
151
Table 10. STATS RESOURCE Memory Display Definitions (cont.)
Item Definition
I/O cache pages
Total I/O cache pages, both used and unused.
Number of pages not accounted for
Pages that cannot be currently accounted for. Because of the dynamic page usage of CP-S, pages are constantly being assigned to new functions or usages. This number reflects
the number of pages that are currently in a status that STATS is unaware of.
Total physical pages in system
Total pages in the system. This is the system memory size as found by AARDVARK at the lost system boot or recovery.
ST A TS USER SIZE Histogram
The STATS USER SIZE HISTOGRAM provides detailed information about the memory sizes of all users. It creates a histogram plot from the memory sizes of all users in the system. This histogram provides:
o a detailed report of the memory currently assigned to user. in the STATS RESOURCE display for memory.
o a count and a percentage of the memory sizes for various memory size ranges.
The following figure is on example of a STATS USER SIZE histogram.
152 STATS USER SIZE Histogram
Module 6-3
CESe-e0
STATS interval from 08:08:36.94 to 15 : 39 : 12 . 98
"Snap" histogram of user memory sizes
(pages)
/-1-1-1-1-1-1-1-1-1-1\
o
to 5•
500 1~l
6 to 10
•••••••••••••••
16034 37 ~11 to 15
••••••
' - - \ 6903 16 ~16 to 20
••••
'-\ 4251 10 ~)21 to 25
•••••
' - \ 5807 13~l
26 to 30
•
1 540 1 ~31 to 35
•
\ 639 1 ~36 to 40
•
\ 1241Hl
41 to 45
•
1 307 1 ~46 to 50
•••
'-\ 3178 7 ~51 to 55
•
\ 690 2 ~56 to 60
•
1 372 1 ~61 to 65
•
1 98o
~66 to 70
•
1 68 0~71 to 75
•
1 138o
~76 to 80
•
\ 918 2 ~81 to 85
•
\ 1203 3 ~86 to 90
•
1 32o
~91 to 95
•
1 16o
~96 and above
•
\ 633 1 ~\-1-1-1-1-1-1-1-1-1-1/
43568
Figure 17. STATS USER SIZE Histogram
Memory Tuning
The CONTROL processor AUTOSHARE and MAXMM parameters are used in memory tuning.