Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Interpretting the result of TOP command Post 7249 by Perderabo on Friday 21st of September 2001 03:58:30 PM
Old 09-21-2001
If you and I are on the system and we both run vi to edit different files, no modern kernel will give us two complete seperate copies of vi. The program's memory will be broken into segments. The text segment contains (roughly) the code and the unchanging constants. We will share one text segment bewteen us. We each get a data segment and we each get a stack. top will report the total of all the segments for each process, but you can't add them up and expect that system needs to use that much physical memory. With shared libraries, it get a bit more confused. If you use emacs and I use vi, will we have different text segments, but we both might be using the same copy of printf and other library functions. Oracle is probably using shared memory which further complicates things. Shared memory is another memory segment, and again many processes can map that seqment into their memory space. So 100 copies of a 700 MB program might easily fit in a couple of GB of memory.

In view of all this, it really isn't possible anymore to truly say how much memory a single process is using in the sense that you want. Each process really is using 700MB, but they are sharing very large chucks of this with other processes.

Most versions of top have a line that shows system-wide memory usage.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Top command

Hey, Using one single line of command i am trying to show the CPU usage for 4 processors and then filter it out and write it to a text file. Everything seams ok except that i am not able to switch from having the top command show me all CPU processes seperate opposed to showing me the average of... (8 Replies)
Discussion started by: Georgesaa
8 Replies

2. Shell Programming and Scripting

Top command

Hi , can some one please assist me in using top command im facing following after using top: # top -hv UX:sh (top): ERROR: top: syntax error at line 1: `(' unexpected # top -p UX:sh (top): ERROR: top: syntax error at line 1: `(' unexpected thanks in advance (3 Replies)
Discussion started by: NIMISH AGARWAL
3 Replies

3. AIX

Top command in AIX 4.2 (no topas, no nmon, no top)?

Is there a 'top' command equivalent in AIX 4.2 ? I already checked and I do not see the following ones anywhere: top nmon topas (1 Reply)
Discussion started by: Browser_ice
1 Replies

4. Shell Programming and Scripting

Command to find the Memory and CPU utilization using 'top' command

Hi all, I found like top command could be used to find the Memory and CPU utilization. But i want to know how to find the Memory and CPU utilization for a particular user using top command. Thanks in advance. Thanks, Ananthi.U (2 Replies)
Discussion started by: ananthi_ku
2 Replies

5. Shell Programming and Scripting

awk top not getting the "k" result

Hi all, I have the script : top -n 1 | awk '{ if (NR==4) print $5 }' It will return me with one memory usage : for instance 3134720k However, I need to be returned only the number : 3134720 Does anyone knows how to fix the script that return the number (without k) thank you (3 Replies)
Discussion started by: peuceul
3 Replies

6. UNIX for Dummies Questions & Answers

Preserving the format of top command result

hi, I have tried the below command in RHEL5: top|mailx -s "test" "abc@cvf.com" But in the mail the content was not in proper format. Is there any way to preserve the format ? Thanks (2 Replies)
Discussion started by: pandeesh
2 Replies

7. UNIX for Advanced & Expert Users

Analyzing Linux's top command's result

RHEL 5.4 What are the first things you would look for when analyzing Linux's top command output? Below is a top output from one of our Linux machines; Do you see anything wrong? top - 15:56:01 up 133 days, 5:55, 5 users, load average: 2.94, 2.93, 6.58 Tasks: 178 total, 2 running,... (2 Replies)
Discussion started by: John K
2 Replies

8. Shell Programming and Scripting

Grep command giving different result for different users for same command

Hello, I am running below command as root user #nodetool cfstats tests | grep "Memtable switch count" Memtable switch count: 12 Where as when I try to run same command as another user it gives different result. #su -l zabbix -s /bin/bash -c "nodetool cfstats tests | grep "Memtable switch... (10 Replies)
Discussion started by: Pushpraj
10 Replies

9. Shell Programming and Scripting

Top command

Hi All, i am using the below command and once get the output and i need to keep the first batch only.in this case how to do this one. please help me on thistop -b -n 5 >top.txt Thanks, (3 Replies)
Discussion started by: bmk
3 Replies

10. Shell Programming and Scripting

Linux find command seems to not transmit all the result to the '-exec command'

Hello. From a script, a command for a test is use : find /home/user_install -maxdepth 1 -type f -newer /tmp/000_skel_file_deb ! -newer /tmp/000_skel_file_end -name '.bashrc' -o -name '.profile' -o -name '.gtkrc-2.0' -o -name '.i18n' -o -name '.inputrc' Tha command... (3 Replies)
Discussion started by: jcdole
3 Replies
PS(1)							      General Commands Manual							     PS(1)

NAME
ps - process status SYNOPSIS
ps [ acgklnrtuwxU# [ core [ swap [ system ] ] ] ] DESCRIPTION
Ps prints certain indicia about active processes. To get a complete printout on the console or lpr, use ``ps axlw'' For a quick snapshot of system activity, ``ps au'' is recommended. A hyphen may precede options with no effect. The following options may be specified. a asks for information about all processes with terminals (ordinarily only one's own processes are displayed). c causes only the comm field to be displayed instead of the arguments. (The comm field is the tail of the path name of the file the process last exec'ed.) This option speeds up ps somewhat and reduces the amount of output. It is also more reliable since the process can't scribble on top of it. g asks for all processes. Without this option, ps only prints ``interesting'' processes. Processes are deemed to be uninteresting if they are process group leaders, or if their arguments begin with a `-'. This normally eliminates shells and getty processes. k causes the file /usr/sys/core is used in place of /dev/kmem and /dev/mem. This is used for postmortem system debugging. l asks for a long listing. The short listing contains the user name, process ID, tty, the cumulative execution time of the process and an approximation to the command line. n asks for numeric rather than symbolic wchans. This flag implies the ``l'' flag. r asks for ``raw'' output. A non-human readable sequence of structures is output on the standard output. There is one structure for each process, the format is defined by <psout.h> tttyname restricts output to processes whose controlling tty is the specified ttyname (which should be specified as printed by ps, including t? for processes with no tty). This option must be the last one given. u A user oriented output is produced. This includes the name of the owner of the process, process id, nice value, size, tty, cpu time used, and the command. w tells ps you are on a wide terminal (132 columns). Ps normally assumes you are on an 80 column terminal. This information is used to decide how much of long commands to print. The w option may be repeated, e.g. ww, and the entire command, up to 128 characters, will be printed without regard to terminal width. x asks even about processes with no terminal. U causes ps to update a private database where is keeps system information. Thus ``ps -U'' should be included in the /etc/rc file. # A process number may be given, (indicated here by #), in which case the output is restricted to that process. This option must also be last. A second argument tells ps where to look for core if the k option is given, instead of /usr/sys/core. A third argument is the name of a swap file to use instead of the default /dev/swap. If a fourth argument is given, it is taken to be the file containing the system's namelist. Otherwise, ``/unix'' is used. The output is sorted by tty, then by process ID. The long listing is columnar and contains F Flags associated with the process. These are defined by #define lines in /usr/include/sys/proc.h. S The state of the process. 0: nonexistent; S: sleeping; W: waiting; R: running; I: intermediate; Z: terminated; T: stopped. UID The user id of the process owner. PID The process ID of the process; as in certain cults it is possible to kill a process if you know its true name. PPID The process ID of the parent process. CPU Processor utilization for scheduling. PRI The priority of the process; high numbers mean low priority. NICE Used in priority computation. ADDR The memory address of the process if resident, otherwise the disk address. SZ The size in blocks (512 bytes) of the memory image of the process. WCHAN The event for which the process is waiting or sleeping; if blank, the process is running. TTY The controlling tty for the process. TIME The cumulative execution time for the process. COMMAND The command and its arguments. A process that has exited and has a parent, but has not yet been waited for by the parent is marked <defunct>. Ps makes an educated guess as to the file name and arguments given when the process was created by examining memory or the swap area. The method is inherently some- what unreliable and in any event a process is entitled to destroy this information, so the names cannot be counted on too much. FILES
/unix system namelist /dev/kmem kernel memory /dev/swap swap device /usr/sys/core core file /dev searched to find swap device and tty names /var/run/psdatabase system namelist and device information SEE ALSO
kill(1), w(1), pstat(8) BUGS
Things can change while ps is running; the picture it gives is only a close approximation to reality. Some processes, typically those in the background, are printed with null or garbaged arguments, even though the process has not swapped. (Sometimes ps even loses on its own arguments!) In these cases, the name of the command is printed in parentheses. When automatic crash dumps are enabled, /usr/sys/core is not a sensible default core file name. 3rd Berkeley Distribution PS(1)
All times are GMT -4. The time now is 02:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy