06-17-2013
Quote:
Originally Posted by
sunnys7143
Then RSS can utilize/extend to maximum size of memory in SWAP ... correct ??
The RSS value is always less than or equal than the SWAP value, but both of these are dynamic.
SWAP is not a hard limit as the process is free to allocate more memory, i.e. increase its prtstat SWAP value.
Quote:
here my scenario is, some of the processes are getting crashed when RSS size almost reaches SWAP size, then it cannot allocate new memory in it..
correct me if im wrong.
Your process should be able to allocate more virtual memory unless the OS has no more virtual memory free or if the process itself has a hard limit configured (eg: java -Xmx).
Use "swap -s" to figure it out.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
The last line of prstat shows load average.
I am unable to figure out what actually it is.
I have read the man pages and also googled, all for no use.
Can somebody help me, as to what should be the avg. load of the system for best performance and how is this load of prstat calculated. (6 Replies)
Discussion started by: vibhor_agarwali
6 Replies
2. Post Here to Contact Site Administrators and Moderators
Could RSS-support mod be installed for this forum? (3 Replies)
Discussion started by: eugrus
3 Replies
3. Solaris
Hello and thanks in advance.
I have a Sun box with raid 1 on the O/S disks using solaris svm.
I want to unmirror my swap partition, and add the slice on the second disk as an additional swap device. This would give me twice as much swap space.
I have been warned not to do this by some... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
4. Solaris
Good Evening everyone,
I am confused about prstat O/P as it shows memory values which are different from actual value.Below is the O/P of prstat command and swap commands.
NPROC USERNAME SIZE RSS MEMORY TIME CPU
48 root 2113M 1590M 1.2% 45:09.39 32%
31 daemon ... (7 Replies)
Discussion started by: vvpotugunta
7 Replies
5. Red Hat
free -m : 1023 total swap space
created default partition /dev/sdb1 50M using fdisk. i did write the changes.
#mkswap /dev/sdb1
#swapon /dev/sdb1
free -m : 1078 total swap space
this shows that the swap is on
Question : i did not change the type LINUX SWAP (82) in fdisk.
so why is... (5 Replies)
Discussion started by: dplinux
5 Replies
6. HP-UX
Hi
I have an integrity machine rx7620 and rx8640 running hp-ux 11.31. I'm planning to fine tune the system:
- I would like to know when does the memory swap space spill over to the device swap space?
- And how much % of memory swap utilization should be specified (swap space device... (6 Replies)
Discussion started by: lamoul
6 Replies
7. Solaris
Hi,
I have some question about memory in Solaris.
How it's possible that prstat -a show me that some process using 230M RSS and when I'm using pmap -x show me that this same process using only 90M RSS ? (0 Replies)
Discussion started by: deivo
0 Replies
8. Solaris
Hi everyone,
was hoping someone might be able to help me understand what I am seeing on one of our solaris systems.
prstat -s size -a is showing user oradba as being top virtual memory consumption.
639 oradba 3012G 2951G 100% 59:44:01 25%
why is it saying 3012G size and 2951G RSS... (6 Replies)
Discussion started by: k4boy
6 Replies
9. Solaris
Hi,
When I sum the RSS number in the ps command for a specific user and compare it with the RSS values of the prstat command of the same user - there is a big difference.
Server details: Solaris 10 5/09 s10s_u7wos_08 SPARC
prstat output:
NPROC USERNAME SWAP RSS MEMORY TIME ... (2 Replies)
Discussion started by: amitlib
2 Replies
10. Solaris
Hi Solaris Folks :),
I need to calculate the swap usage on solaris server, please let me understand the output of below swap -s and swap -l commands.
$swap -s
total: 1774912k bytes allocated + 240616k reserved = 2015528k used, 14542512k available
$swap -l
swapfile dev swaplo... (6 Replies)
Discussion started by: seenuvasan1985
6 Replies
LEARN ABOUT CENTOS
systemd.swap
SYSTEMD.SWAP(5) systemd.swap SYSTEMD.SWAP(5)
NAME
systemd.swap - Swap unit configuration
SYNOPSIS
swap.swap
DESCRIPTION
A unit configuration file whose name ends in ".swap" encodes information about a swap device or file for memory paging controlled and
supervised by systemd.
This man page lists the configuration options specific to this unit type. See systemd.unit(5) for the common options of all unit
configuration files. The common configuration items are configured in the generic [Unit] and [Install] sections. The swap specific
configuration options are configured in the [Swap] section.
Additional options are listed in systemd.exec(5), which define the execution environment the swapon(8) binary is executed in, and in
systemd.kill(5), which define the way the processes are terminated, and in systemd.resource-control(5), which configure resource control
settings for the processes of the service.
Swap units must be named after the devices or files they control. Example: the swap device /dev/sda5 must be configured in a unit file
dev-sda5.swap. For details about the escaping logic used to convert a file system path to a unit name, see systemd.unit(5).
All swap units automatically get the appropriate dependencies on the devices or on the mount points of the files they are activated from.
Swap units with DefaultDependencies= enabled implicitly acquire a conflicting dependency to umount.target so that they are deactivated at
shutdown.
FSTAB
Swap units may either be configured via unit files, or via /etc/fstab (see fstab(5) for details). Swaps listed in /etc/fstab will be
converted into native units dynamically at boot and when the configuration of the system manager is reloaded. See systemd-fstab-
generator(8) for details about the conversion.
If a swap device or file is configured in both /etc/fstab and a unit file, the configuration in the latter takes precedence.
Unless the noauto option is set for them all swap units configured in /etc/fstab are also added as requirements to swap.target, so that
they are waited for and activated during boot.
OPTIONS
Swap files must include a [Swap] section, which carries information about the swap device it supervises. A number of options that may be
used in this section are shared with other unit types. These options are documented in systemd.exec(5) and systemd.kill(5). The options
specific to the [Swap] section of swap units are the following:
What=
Takes an absolute path of a device node or file to use for paging. See swapon(8) for details. If this refers to a device node, a
dependency on the respective device unit is automatically created. (See systemd.device(5) for more information.) If this refers to a
file, a dependency on the respective mount unit is automatically created. (See systemd.mount(5) for more information.) This option is
mandatory.
Priority=
Swap priority to use when activating the swap device or file. This takes an integer. This setting is optional.
TimeoutSec=
Configures the time to wait for the swapon command to finish. If a command does not exit within the configured time, the swap will be
considered failed and be shut down again. All commands still running will be terminated forcibly via SIGTERM, and after another delay
of this time with SIGKILL. (See KillMode= in systemd.kill(5).) Takes a unit-less value in seconds, or a time span value such as "5min
20s". Pass 0 to disable the timeout logic. Defaults to TimeoutStartSec= in manager configuration file.
Check systemd.exec(5) and systemd.kill(5) for more settings.
SEE ALSO
systemd(1), systemctl(8), systemd.unit(5), systemd.exec(5), systemd.kill(5), systemd.resource-control(5), systemd.device(5),
systemd.mount(5), swapon(8), systemd-fstab-generator(8), systemd.directives(7)
systemd 208 SYSTEMD.SWAP(5)