Sponsored Content
Full Discussion: vmstat -P (physical memory)
Top Forums UNIX for Advanced & Expert Users vmstat -P (physical memory) Post 302068832 by gfhgfnhhn on Tuesday 21st of March 2006 07:40:11 AM
Old 03-21-2006
Error vmstat -P (physical memory)

vmstat -P commands gives me an output as shown at the end of this message.

my first question is about the difference between "total physical memory" and "total physical memory use"

"Total Physical Memory" -"Total Physical Memory Use"
524288 pages-524026 pages= 262 pages

does it mean that 262 pages are free?
if they are not free, this pages are used for what?
if they are free what relation exist between these pages(262 pages) and
the free pages = 18540 (which are mentioned in the
"Managed Pages Break Down" part)

my second question is:
whats the relation between total physical memory(here it is=524288 ) and
the total memory mentioned in the "Managed Pages Break Down" part
(here it is=507442 pages)


vmstat -P output:
***********************

Total Physical Memory = 4096.00 M
= 524288 pages

Physical Memory Clusters:

start_pfn end_pfn type size_pages / size_bytes
0 256 pal 256 / 2.00M
256 130985 os 130729 / 1021.32M
130985 131072 pal 87 / 696.00k
131072 524282 os 393210 / 3071.95M
524282 524288 pal 6 / 48.00k

Physical Memory Use:

start_pfn end_pfn type size_pages / size_bytes
256 289 scavenge 33 / 264.00k
289 1143 text 854 / 6.67M
1143 1306 data 163 / 1.27M
1306 1535 bss 229 / 1.79M
1535 1745 kdebug 210 / 1.64M
1745 1753 cfgmgmt 8 / 64.00k
1753 1755 locks 2 / 16.00k
1755 1769 pmap 14 / 112.00k
1769 4537 unixtable 2768 / 21.62M
4537 4633 logs 96 / 768.00k
4633 7781 vmtables 3148 / 24.59M
7781 131072 managed 123291 / 963.21M
131072 140077 vmtables 9005 / 70.35M
140077 524282 managed 384205 / 3001.60M
============================
Total Physical Memory Use: 524026 / 4093.95M

Managed Pages Break Down:

free pages = 18540
active pages = 170145
inactive pages = 226033
wired pages = 61434
ubc pages = 31290
==================
Total = 507442

WIRED Pages Break Down:

vm wired pages = 28726
ubc wired pages = 0
meta data pages = 5225
malloc pages = 18210
contig pages = 1456
user ptepages = 7316
kernel ptepages = 491
free ptepages = 10
==================
Total = 61434

***********************
***********************
 

10 More Discussions You Might Find Interesting

1. Programming

Physical Memory

Hi, My problem is next.... How can I work with physical memory in the Unix FreeBSD 2.2 or hight? What is the "mem" & "kmem" drivers? P.S./ writing device driver for UNIX FreeBSD 2.2 :D (2 Replies)
Discussion started by: Alex_T
2 Replies

2. UNIX for Dummies Questions & Answers

physical memory

It is just a general question....is there a limit on the memory? I am looking into a process to store image files on the unix server which will be accessed by the application, and I just wonder if there is any limit regarding the physical or virtual memory. I am very new to unix, so thanks for... (1 Reply)
Discussion started by: cchien
1 Replies

3. Shell Programming and Scripting

get physical and virtual memory

What command can i use to get the physical and virtual memory of a database? (7 Replies)
Discussion started by: tads98
7 Replies

4. Solaris

physical memory

what is the command to find the physical memory in soalris OS and how to find whether paging is happening or not ? (2 Replies)
Discussion started by: jayaramanit
2 Replies

5. Solaris

How to find Total and Free Physical Memory and Logical Memory in SOLARIS 9

Hi, Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:- 1. Total Physical Memory in the system(total RAM). 2. Available Physical Memory(i.e. RAM Usage) 3. Total (Logical) Memory in the system 4. Available (Logical) Memory. I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies

6. Filesystems, Disks and Memory

Does vmstat -d give a count of actual physical writes/reads done to/from hard disk?

Hi, I am trying to find the reliability of 'vmstat -d' for showing the actual physical writes on sectors on hard disk. Can anyone please tell me if the numbers in the "sectors" field under "read" or "write" headers show a count of the actual write commands sent to disk from the low level... (2 Replies)
Discussion started by: jake24
2 Replies

7. Solaris

restrcit physical memory with zone.max-locked-memory

Is it possible to restrict physical memory in solaris zone with zone.max-locked-memory just like we can do with rcapd ? I do not want to used rcapd (1 Reply)
Discussion started by: fugitive
1 Replies

8. AIX

memory usage with vmstat

Hi Admins, Management asked me to submit last 3 months memory usage as part of quaterly capacity report.Last month only we have configured monitoring tool.So i cant use the tool to obtain the data.What i have is vmstat output for the last 3 months. How can i calculate memory usage using... (1 Reply)
Discussion started by: newaix
1 Replies

9. AIX

Physical Memory expansion

IBM says we cannot expand our physical memory on our 570's without upgrading all the existing DIMMS since all slots are currently full. Is it really so difficult for IBM to build servers that leave a couple vacant slots for future expansion? A technical explanation would be greatly appreciated.... (2 Replies)
Discussion started by: 1computerman
2 Replies

10. Solaris

Physical memory calculation

Below is Physical Memory result : -bash-3.00$ prtconf | grep "Memory size" Memory size: 36854 Megabytes -bash-3.00$ vmstat 1 2 | tail -1 0 0 0 28220616 1318888 15 143 0 0 0 0 0 253 2 15 0 5215 14989 5917 7 0 93 and the script i have to calculate this in Percentage is : #!/bin/sh... (3 Replies)
Discussion started by: mjoshi010207
3 Replies
vmstat(1)						      General Commands Manual							 vmstat(1)

NAME
vmstat - Displays virtual memory statistics SYNOPSIS
vmstat interval [count] vmstat [-D | -f | -i | -M | -p | -P | -r rad_id | -R | -s | -w] The vmstat command displays system statistics for virtual memory, processes, trap, and CPU activity. OPTIONS
Displays debugging information if kmem_debug is set. Displays only statistics about the number of forks since system startup (see the fork() call). Displays the following virtual memory statistics: # vmstat -i Virtual Memory Statistics: (pagesize = 8192) procs memory pages intr cpu r w u act free wire fault cow zero react pin pout in sy cs us sy id 2 82 29 23K 12K 4906 3M 963K 834K 620 710K 0 73 30 391 0 2 98 Displays information about memory usage by buckets. This information can be used for kernel debugging. Displays statistics for the vm and ubc subsystems for all Resource Affinity Domains (RADs). Typical output (derived from a single-RAD, single-CPU server) is shown in the following example: # vmstat -p Total RADs: 1 Total CPUs: 1 Total Ticks: 512 36441297 VM faults 1677 VM kfaults 2115850 VM cowcopy 1677 VM kzfod 0 VM pagesteal 0 VM prewrites 0 VM anon_prewrites 0 VM swap_prewrites 0 VM cleanrecs 0 VM swaprecs 0 VM lmsteal 0 VM lmstealwins 0 VM ffl 0 VM pout_scan 0 VM pout_pagescan 0 VM pout_call 0 VM pout 0 VM pout_target 0 VM pout_burst 12548 VM act_scans 12548 VM act_moves 0 VM lock_fails 0 VM migrations 2547665 VM TOT cowfaults 3813949 VM TOT zfod 0 VM TOT iowrites 0 VM TOT pgwrites 26823910 VM TOT ioreads 0 VM TOT pgreads 1423 VM TOT reactivate 0 UBC allocscans 0 UBC alloceol 0 UBC allocpush 0 UBC allocstole 0 UBC allocseq 0 UBC wacalls 0 UBC wascans 0 UBC waeol 0 UBC prges 0 UBC prgscans 0 UBC prgeol 0 UBC prgburst 0 UBC prgfree 0 UBC mmapfree 79566 UBC wdeny 0 UBC hardsteals 0 UBC stealscans 0 UBC dirtywra 0 UBC reclaim 0 UBC pagesteal 42127497 UBC lookups 41985615 UBC lookuphits 0 UBC ffl 0 UBC lmsteal 0 UBC lmstealwins 0 UBC seqdrain 144957 UBC TOT alloc 0 UBC TOT iowrites 0 UBC TOT reactivate 0 UBC TOT pgwrites Displays the following accumulated statistics about physical memory use: Sum of the total physical memory in the machine. This statistic describes how physical memory is clustered. It shows where memory is being used (pal, os, and nvram), the starting and ending pageframes, and the total amount of memory used. This statistic shows a breakdown of physical memory used by the operating system (such as text, data, and bss). It contains the starting and ending pageframes, memory usage per category, and total memory used. This statistic provides snap- shot of where managed physical memory resides when the vmstat command was run. It indicates the the number of pages in the free, active and inactive queues, the number of wired pages, and the number of pages held in the unified buffer cache (UBC). This statistic describes the physical pages that are wired in memory. The fields show the number of wired pages in anonymous(vm) memory, the UBC, pages used for meta data, the kernel malloc pools, contiguous memory, and pages used for page table entries (ptes). The display typically shows: vm and ubc wired pages meta data, malloc, and contig pages user, kernel, and free ptepages. Displays virtual memory statistics for the specified Resource Affinity Domain (RAD) only. The rad_id is an integer assigned automatically by the system. Typical output is shown in the follow- ing example, which has been reformatted for ease of reference: # vmstat -r 0 Virtual Memory Statistics: (pagesize = 8192) procs memory pages RAD r w u st sw act actv actu acti free wire wirv wiru fault 0 2 157 27 0 0 31K 4928 18K 8813 24K 6544 3015 0 36M intr cpu cow zero react pin pout in sy cs us sy id 2M 3M 1423 26M 0 102 249 229 0 1 99 Displays information for all Resource Affinity Domains (RADs). Typical output is shown under the -r option. Displays the following accumulated statistics along with the page size: Total number of pages that are currently in use but can be used for paging. Total number of VM pages that are allocated but are most likely to be used for paging. Total number of unreferenced (clean) pages that are available for use. Total number of pages that are currently in use and cannot be used for paging (not a real list). Number of address translation faults that have occurred. Number of copy-on-write page faults, which occur if the requested page is shared by a parent process and one or more child processes (using the fork function) and if one of the processes needs to modify the page. In this case, VM loads a new address into the translation buffer and copies the contents of the requested page into the new address for modification by the process. Number of zero-filled-on-demand page faults, which occur if VM cannot find the page in the inter- nal data structures and if the requested page is new and has never been referenced. In this case, VM initializes a physical page (the con- tents of the page are zeroed out) and loads the address into the page table. Number of pages that have been faulted while on the inactive list. Number of requests for pages from a pager. Number of pages that have been paged out. Number of task and thread context switches. Number of nonclock device interrupts. Number of system calls called. Appends iowait information to the default output as follows:. Vir- tual Memory Statistics: (pagesize = 8192) procs memory pages intr cpu r w u act free wire fault cow pin pout in sy cs us sy id iowait 2 82 29 23K 12K 4905 3M 963K 710K 0 73 30 391 0 2 98 0 DESCRIPTION
The value of interval is a time in seconds, causing vmstat to display statistics at the specified interval. The first report generated includes statistics for the time since the last reboot. Each subsequent report is for the specified interval only. If you specify count after interval, it specifies the number of reports generated. For example, vmstat 1 10 produces 10 reports at 1-second intervals. You cannot specify count without interval, since the first numeric argument to vmstat is always assumed to be interval. At any time, system memory can be in use by the kernel in kseg, wired (pages that are currently in use and cannot be used for paging), on the active list (pages that are currently in use but can be used for paging), on the inactive list (pages that are allocated but are most likely to be used for paging), on the free list (pages that are clean and available for use), or used by the Unified Buffer Cache (UBC). The vmstat command does not report on the memory in kseg and memory used by the UBC. The following values are displayed: Process information: Number of threads that are running or are runnable. Number of threads waiting interruptibly. Number of threads wait- ing uninterruptibly. Virtual memory information: Total number of pages on the active list, the inactive list (pages that are allocated but are most likely to be used for paging), and the Unified Buffer Cache (UBC) least recently used (LRU) list. Total number of pages that are clean and available for use. Total number of pages that are currently in use and cannot be used for paging (not a real list). Number of address translation faults that have occurred. Number of copy-on-write page faults, which occur if the requested page is shared by a parent process and one or more child processes (using the fork function) and if one of the processes needs to modify the page. In this case, VM loads a new address into the translation buffer and copies the contents of the requested page into the new address for modification by the process. Number of zero-filled-on-demand page faults, which occur if VM cannot find the page in the internal data structures and if the requested page is new and has never been referenced. In this case, VM initializes a physical page (the contents of the page are zeroed out) and loads the address into the page table. Number of pages that have been faulted while on the inactive list. Number of requests for pages from a pager. Number of pages that have been paged out. Interrupt information: Number of nonclock device interrupts per second. Number of system calls called per second. Number of task and thread context switches per second. CPU information: Percentage of user time for normal and priority processes. Percentage of system time. Percentage of idle time. Percent- age of iowait. If the -w option is not specified, the iowait time is included in the id statistic. Specify -f to display fork statistics only. Specify -s for a single display of accumulated statistics, as well as page size. SEE ALSO
Commands: iostat(1), sysman(8) vmstat(1)
All times are GMT -4. The time now is 12:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy