Sponsored Content
Operating Systems AIX High Runqueue (R) LOW CPU LOW I/O Low Network Low memory usage Post 302589697 by zaxxon on Thursday 12th of January 2012 11:21:42 AM
Old 01-12-2012
What applications running there? Is SMT activated? What OS level do you have (latest fix pack installed?)? Is that always, only at peak times? What has changed since? More info would be helpful, thanks.
 

10 More Discussions You Might Find Interesting

1. Solaris

Low average cpu utilization.

Hi to all, i have an app on solaris 5.8 writed in C++ (3.2.1) that use multi threading. Hardware has 8 cpu. When i run my app i note that the average of cpu go at least at 40%, and the performance are not so higher.. There is a cpu limitation on solaris, that dedicate only a part of cpu... (3 Replies)
Discussion started by: Moodie
3 Replies

2. Solaris

malloc returning NULL if freemem high & swapmem low

Hi All, In my application malloc is returning NULL even though there is sufficient amount of free memory is available but swap memory is low. Is this possible that, if free memory is high & swap memory is low, malloc will not be able to allocate memory & return NULL ?:) Kindly look into... (5 Replies)
Discussion started by: Ritesh Kumar
5 Replies

3. Shell Programming and Scripting

low & high values

on the file Ftp'd from the mainframe ,do we have any UNIX command to replace mainframe low and values to space or null. i tried using tr and it doesn't work ... Thanks (1 Reply)
Discussion started by: rlmadhav
1 Replies

4. Shell Programming and Scripting

Picking high and low variables in a bash script - possible?

Is it possible to have a bash script pick the highest and lowest values of four variables? I've been googling for this but haven't come up with anything. I have a script that assigns variables ($c0, $c1, $c2, and $c3) based on the coretemps from grep/sed statements of sensors. I'd like to also... (5 Replies)
Discussion started by: graysky
5 Replies

5. Shell Programming and Scripting

Split file into chunks of low & high byte

Hi guys, i have a question about spliting a binary file into 2 chunks. First chunk with all high bytes and the second one with all low bytes. What unix tools can i use? And how can this be performed? I looked in manpages of split and dd but this does not help. Thanks (2 Replies)
Discussion started by: basta
2 Replies

6. HP-UX

Bad performance but Low CPU loading?

There might be some problem with my server, because every morning at 7, it's performance become bad with no DB extra deadlock. But I just couldn't figure it out. Please give me some advise, thanks a lot... According to the CPU performace chart, Daily CPU loading Maximum: 42 %, Average:36%. ... (8 Replies)
Discussion started by: GreenShery
8 Replies

7. UNIX for Dummies Questions & Answers

Kernel/ user space and high/ low mem

Need some clarification on this.... 1. how are kernel/ user spaces and high/low memory related? 2. What do they all mean when i have the kernel command line as: "console=ttyS0,115200 root=/dev/sda2 rw mem=exactmap memmap=1M@0 memmap=96M@1M irqpoll" or 2. what do mem and memmap mean in... (3 Replies)
Discussion started by: dragonpoint
3 Replies

8. AIX

Low Virtual memory available

Hi I am running AIX 5.2. My server is running low on memory. It it using about 1307775 file pages on a total of 1511424 (from vmstat -v). I looked at the memory yesterday morning, and we had plenty of free memory. I did a backup from Windows (ftp mget command) of a large file selection. From... (5 Replies)
Discussion started by: fredrivard
5 Replies

9. Red Hat

High RAM usage, extremely low swapping

Hi team I have three physical servers running on Red Hat Enterprise Linux Server release 6.2 with the following memory conditions: # cat /proc/meminfo | grep -i mem MemTotal: 8062888 kB MemFree: 184540 kB Shmem: 516 kB and the following swap conditions: ... (6 Replies)
Discussion started by: hedkandi
6 Replies

10. UNIX for Advanced & Expert Users

Linux live cd for low memory

Could I please get some recommendations of a linux live cd for low memory? (1 Reply)
Discussion started by: cokedude
1 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 04:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy