Sponsored Content
Full Discussion: vmstat question
Top Forums UNIX for Dummies Questions & Answers vmstat question Post 16157 by Perderabo on Tuesday 26th of February 2002 09:29:23 AM
Old 02-26-2002
Well, gosh...runnable means runnable...able to be run. If a process is not runnable it must be waiting for something to occur, like a signal or an i/o operation.

Swapped means that the entire process is sitting on disk in the swap area. If it wasn't swapped, it would be in memory.

Having processes swapped out is not good, it means you really need more memory.

If you really get exactly 30 such processes each time that you shutdown your database, I would guess that they are database processes of some kind that were sleeping, then got swapped, and finally awoken by the shutdown process. But I don't have much to go on here and that is just a guess.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Vmstat

I have MATLAB INSTALLED IN MY SUN MACHINE >> WHENEVER I USE IT THE CPU USAGE SHOWS ABT 90% Seeing the vmstat shows that system calls and context switch counters reach a very high value . What are these counters ( Man pages do not give much info on that) .... The only thing i can make out that... (1 Reply)
Discussion started by: DPAI
1 Replies

2. UNIX for Dummies Questions & Answers

vmstat

Hi, In the unix command, "vmstat" we get information on Page memory. what does the "mf" - "minor fault" is? Regards, Anent (3 Replies)
Discussion started by: anent
3 Replies

3. UNIX for Dummies Questions & Answers

vmstat

When I exeute vmstat (e.g. vmstat 30 2), in some machines I get some wierd result as the first line. like: -117% or 208% for CPU idle percentage. But the second line is alright. Could someone explain this please. Thanks ! Chaadana (4 Replies)
Discussion started by: chaandana
4 Replies

4. UNIX for Advanced & Expert Users

vmstat

Hi, what does mean the free colomne in out put of vmstat ? is it free espace of physical memory or of swap space on hard disk ? Thank you (4 Replies)
Discussion started by: big123456
4 Replies

5. UNIX for Dummies Questions & Answers

vmstat

Hi I wanted to collect data by using vmstat -I 60 >xxxx.txt & using my own account It was stopped by it self after 2 hours try again same result We want to collect day date by succession how to collect data using vmstat for day Thank you (2 Replies)
Discussion started by: Syed_45
2 Replies

6. HP-UX

vmstat question

if I have a two CPU when I run vmstat command to check cpu usage it only one row procs memory page faults cpu r b w avm free re at pi po fr de sr in sy cs us sy id 1 ... (1 Reply)
Discussion started by: alert0919
1 Replies

7. Shell Programming and Scripting

vmstat

Hi I need to write a script to display VMSTAT every 5 seconds and I just need the memory columns - swap free re and just the numbers and the headers arent required. For example bash-3.00$ vmstat 5| awk '{print $4" "$5" "$6}' disk faults cpu ------ This header isnt required swap... (3 Replies)
Discussion started by: kapilk
3 Replies

8. Solaris

Simple question about vmstat

Hi friends, I have confusion about VMSTAT command. 1. When I execute "vmstat" command without any interval then I got something like following output. vmstat procs memory page disk faults cpu r b w swap free re mf pi po fr de sr m1 m1 m1... (13 Replies)
Discussion started by: rahul_switch
13 Replies

9. UNIX for Dummies Questions & Answers

Red Hat Linux question on top and vmstat outputs

RHEL 5.4 Our Linux machine seemed to be running slow. So, I ran the top and vmstat commands. Question1. I can see the process 11517 consuming 100% CPU . But that just means that this process totally utilizes one of the cores in a mult-core CPU. Right ? This machine apparently has two... (2 Replies)
Discussion started by: kraljic
2 Replies

10. AIX

Question on r-queue from vmstat out

On our prod system we found sometime runqueue goes back to 0 as below. Whereas on test server even with very very less work the r-queue never dropped to 0. Under what conditions r-queue drops to 0? Does it mean something unusual? EG: kthr memory page faults ... (1 Reply)
Discussion started by: aixusrsys
1 Replies
RUNQUEUE(9)                                                BSD Kernel Developer's Manual                                               RUNQUEUE(9)

NAME
chooseproc, procrunnable, remrunqueue, setrunqueue -- manage the queue of runnable processes SYNOPSIS
#include <sys/param.h> #include <sys/proc.h> extern struct rq itqueues[]; extern struct rq rtqueues[]; extern struct rq queues[]; extern struct rq idqueues[]; struct thread * choosethread(void); int procrunnable(void); void remrunqueue(struct thread *td); void setrunqueue(struct thread *td); DESCRIPTION
The run queue consists of four priority queues: itqueues for interrupt threads, rtqueues for realtime priority processes, queues for time sharing processes, and idqueues for idle priority processes. Each priority queue consists of an array of NQS queue header structures. Each queue header identifies a list of runnable processes of equal priority. Each queue also has a single word that contains a bit mask identify- ing non-empty queues to assist in selecting a process quickly. These are named itqueuebits, rtqueuebits, queuebits, and idqueuebits. The run queues are protected by the sched_lock mutex. procrunnable() returns zero if there are no runnable processes other than the idle process. If there is at least one runnable process other than the idle process, it will return a non-zero value. Note that the sched_lock mutex does not need to be held when this function is called. There is a small race window where one CPU may place a process on the run queue when there are currently no other runnable processes while another CPU is calling this function. In that case the second CPU will simply travel through the idle loop one additional time before noticing that there is a runnable process. This works because idle CPUs are not halted in SMP systems. If idle CPUs are halted in SMP sys- tems, then this race condition might have more serious repercussions in the losing case, and procrunnable() may have to require that the sched_lock mutex be acquired. choosethread() returns the highest priority runnable thread. If there are no runnable threads, then the idle thread is returned. This func- tion is called by cpu_switch() and cpu_throw() to determine which thread to switch to. choosethread() must be called with the sched_lock mutex held. setrunqueue() adds the thread td to the tail of the appropriate queue in the proper priority queue. The thread must be runnable, i.e. p_stat must be set to SRUN. This function must be called with the sched_lock mutex held. remrunqueue() removes thread td from its run queue. If td is not on a run queue, then the kernel will panic(9). This function must be called with the sched_lock mutex held. SEE ALSO
cpu_switch(9), scheduler(9), sleepqueue(9) BSD November 3, 2000 BSD
All times are GMT -4. The time now is 09:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy