12-04-2013
RSS is "resident set size", the amount of actual RAM a program is using. It's the one to worry about, usually. VSS is the virtual size, which is often far bigger than the amount of memory actually used. Much memory is shared between programs, too, for libraries and such, which inflates the size of VSS even more -- just blindly adding up VSS sizes to a total may add the same memory many times.
The shared memory problem is also true for RSS in fact, which can make programs which have large amounts of data shared, like oracle, difficult to pin down exactly how much they're using at a time.
Last edited by Corona688; 12-04-2013 at 05:00 PM..
10 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Hi There,
I have upgraded the DELL poweredge 2600 server memory from 2GB to 4GB. However, the memory only showed at 2GB of utilization. How to make sure that the server is full utilize of 4GB of memory. Is there the Virtual memory need to be reconfigure as this server is run on windows 2000 and... (2 Replies)
Discussion started by: vestro
2 Replies
2. AIX
Hi friends..
Help to solve this issue...
Is there any parameter setting to control or limit the size of the shared memory a process can attach for the below specified environment?
The man pages says it can attach upto segments of size 2GB. But when our process (which also connects to... (0 Replies)
Discussion started by: sdspawankumar
0 Replies
3. Linux
Hi all,
I was compiling my glibc 2.6.1 source files on a new kernel 2.66.22.6 and it seems that i am running into issues with the Virtual Memory. It displays the error message:
virtual memory exhausted: Cannot allocate memory
I saw an article on how to adjust the parameters but i can't... (5 Replies)
Discussion started by: scriptingmani
5 Replies
4. Solaris
One of our project has exceeded its assigned max-memory-locked by 3 times .. The said project is using around 9 gigs as described by rss parameter in prstat -J .. and the max-project-memory parameter has been defined as 3gigs .. is it normal or we are monitoring the project memory usage in wrong... (2 Replies)
Discussion started by: fugitive
2 Replies
5. AIX
Currently server have load while there is no heavy things running, just oracle database/ application server oracle. I don't understand why server have heavy load, 22GB is under buffer, how to clean buffer/memory in AIX
load averages: 9.42, 9.43, 9.68; 05:25:08
141 processes: 125 idle, 16... (12 Replies)
Discussion started by: learnbash
12 Replies
6. Solaris
We have a zone configured in our X4600 machine with memory capped to 16GB. Most of the time zone is running with high physical memory utilization. It seems from "top" command shows that the command "kernel" is locks 15GB phy. memory and not using swap memory. Whenever we restart the application... (2 Replies)
Discussion started by: rock123
2 Replies
7. SuSE
I have parallels container running on Suse. From top command, I am not able to see, what is eating up so big amount of memory.
top - 07:44:24 up 172 days, 18:52, 1 user, load average: 0.01, 0.02, 0.00
Tasks: 44 total, 1 running, 43 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0%us, ... (1 Reply)
Discussion started by: solaris_1977
1 Replies
8. AIX
I have a server with 300Gb allocated to it. Some times I observed in topas
Comp% 73 and Non comp 35% and client is also 35% and my paging is showing 92%. If my physical memory utilized only 70% then why paging is so high.
And what is relation between Comp, noncomp and client? If the memory... (1 Reply)
Discussion started by: powerAIX
1 Replies
9. Linux
Hi,
In our production box i can see the Swap space using the below command
free
total used free shared buffers cached
Mem: 65963232 41041084 24922148 0 877160 35936292
-/+ buffers/cache: 4227632 61735600
Swap: 4192880 ... (6 Replies)
Discussion started by: ratheeshjulk
6 Replies
10. Shell Programming and Scripting
I am getting a out of memory issue while executing the perl program.
Per version : /opt/acc_perl/lib/site_perl/5.14.2
Read in 54973 total records
Read in 54973 table records from table.
Out of memory!
so the job get failed due to out of memory. need to get rid of the out of memory... (3 Replies)
Discussion started by: ramkumar15
3 Replies
SHMGET(2) BSD System Calls Manual SHMGET(2)
NAME
shmget -- get shared memory area identifier
SYNOPSIS
#include <sys/shm.h>
int
shmget(key_t key, size_t size, int shmflg);
DESCRIPTION
shmget() returns the shared memory identifier associated with the key key.
A shared memory segment is created if either key is equal to IPC_PRIVATE, or key does not have a shared memory segment identifier associated
with it, and the IPC_CREAT bit is set in shmflg.
If a new shared memory segment is created, the data structure associated with it (the shmid_ds structure, see shmctl(2)) is initialized as
follows:
o shm_perm.cuid and shm_perm.uid are set to the effective uid of the calling process.
o shm_perm.gid and shm_perm.cgid are set to the effective gid of the calling process.
o shm_perm.mode is set to the lower 9 bits of shmflg.
o shm_lpid, shm_nattch, shm_atime, and shm_dtime are set to 0
o shm_ctime is set to the current time.
o shm_segsz is set to the value of size.
o The ftok(3) function may be used to generate a key from a pathname.
RETURN VALUES
Upon successful completion a positive shared memory segment identifier is returned. Otherwise, -1 is returned and the global variable errno
is set to indicate the error.
ERRORS
The shmget() system call will fail if:
[EACCES] A shared memory segment is already associated with key and the caller has no permission to access it.
[EEXIST] Both IPC_CREAT and IPC_EXCL are set in shmflg, and a shared memory segment is already associated with key.
[EINVAL] No shared memory segment is to be created, and a shared memory segment exists for key, but the size of the segment associ-
ated with it is less than size, which is non-zero.
[ENOENT] IPC_CREAT was not set in shmflg and no shared memory segment associated with key was found.
[ENOMEM] There is not enough memory left to created a shared memory segment of the requested size.
[ENOSPC] A new shared memory identifier could not be created because the system limit for the number of shared memory identifiers
has been reached.
LEGACY SYNOPSIS
#include <sys/types.h>
#include <sys/ipc.h>
#include <sys/shm.h>
int
shmget(key_t key, int size, int shmflg);
All of these include files are necessary. The type of size has changed.
SEE ALSO
ftok(3), shmat(2), shmctl(2), shmdt(2), compat(5)
BSD
August 17, 1995 BSD