Sponsored Content
Full Discussion: Limit RAM Usages
Operating Systems Linux Red Hat Limit RAM Usages Post 302630509 by sds9985 on Thursday 26th of April 2012 12:27:44 AM
Old 04-26-2012
Shirish,

For test purposes, the easiest way to effectively reduce the amount of physical RAM available for use by processes is to crank up the kernel parameter vm.min_free_kbytes. This sets the low water mark for the amount of memory held as free for new processes and is normally set to something like 50MB. Turning this up to 3.5GB in your example will mean the system will run out of physical memory and start actively paging very quickly. See the man pages for sysctl and sysctl.conf.

This parameter is also very useful for effectively eliminating cache and buffer space when testing I/O throughput.

Of course, the whole point of designing a system configuration is to ensure that the system would only ever actively page as an absolute last resort, one small step better than crashing. Systems should NEVER actively page in normal operation. Disk I/O (milliseconds) is literally a million times slower than RAM operations (nanoseconds), so system performance will immediately become completely unacceptable as soon as the system starts to actively page.

Active paging (shown by "sar -B" or "vmstat") is completely different from swap space usage (shown by "sar -S" or "free"). It's OK for a system to statically park pages of memory for long inactive processes on the swap partition. But, if the system is actively paging, it's reading and writing thousand of blocks to and from swap space per second.

If you even suspect that this system will start actively paging under heavy load, BUY MORE RAM.

Remember to reset vm.min_free_kbytes to the original value when your tests are complete...

Last edited by sds9985; 04-26-2012 at 01:34 AM..
This User Gave Thanks to sds9985 For This Post:
 

10 More Discussions You Might Find Interesting

1. Programming

getting RAM size

Sir, How can i get the RAM size .Is there is any predefined function ..Howsir??? Thanks In advance, ArunKumar (6 Replies)
Discussion started by: arunkumar_mca
6 Replies

2. Solaris

Usages of Array's (Important please)

;) Hi friends, any one please help me. I want to store some job names into an array and also I want extract these names on different timings for scheduling. Please give me some idea. your's loving LOVE :p (1 Reply)
Discussion started by: Love
1 Replies

3. Linux

Built in ram limit for 64 bit

Hey all, I have been thinking about getting a new computer, and the motherboard I am looking at is capable of holding up to 8 Gb of ram. Now it appears as though for 32 bit linux, in order to use more than 4 Gb of ram, you had to enable a certain option in the kernel, but if I remember... (2 Replies)
Discussion started by: kermit
2 Replies

4. Red Hat

red hat Linux 5.0 is detecting 3gb ram but physical ram is 16gb

Hi, On server 64bit Hw Arch , Linux 5.0(32bit) is installed it is showing only 3gb of ram though physical is 16gb can u give me idea why? (4 Replies)
Discussion started by: manoj.solaris
4 Replies

5. AIX

[AIX] usages of lint for .cpp file?

Hi , I Want to apply AIX lint to my source code which all are *.cpp/*.h >lint test.cpp lint: 1286-332 File test.cpp must have a .c, .C or .ln extension. It is ignored. lint: 1286-334 There are no files to process. I am getting above error. -Ashok (3 Replies)
Discussion started by: ashokd001
3 Replies

6. Solaris

How get memory and cpu usages of user's processes?

I have the processes (100+) by the oracle id and I'd to get the summarized view of the oracle processes' usage of the memory and the cpu. top would give me some, but not all. Thanks (3 Replies)
Discussion started by: iwmi
3 Replies

7. Solaris

Limit: stacksize: Can't remove limit

Hi all, I'm using to Solaris machine. When I run a simple script this messenger come out:"limit: stacksize: Can't remove limit". Any one know the way to resolve this problem without reboot the machine? Thanks in advance. (3 Replies)
Discussion started by: Diabolist9
3 Replies

8. Red Hat

Physical RAM

Hi, I have a server (BL460c) with 32G of physical RAM. It currently only uses approx 5% its capacity but will use more (not sure how much more) pending the launch of further applications. If I need to build another node of similar functionality should I consider downgrading the physical... (2 Replies)
Discussion started by: Duffs22
2 Replies

9. Shell Programming and Scripting

help me for Perl script for tool usages

Hi, How to do Perl script for floating license usages metric. Anyone help me out this issue? Regards, Ram. (0 Replies)
Discussion started by: ramanthan
0 Replies

10. Cybersecurity

Limit CPU and RAM utilization for new user in RedHat

We have a system with 4 Xeon Processors each with 10 cores, total 512 GB RAM and 10 TB Hard Drive. we want to create multiple user accounts with different resource limitations as : User 1: RAM : 50GB, PROCESSOR: 10 Cores , User folder in home directory of 10GB space. User 2: RAM :... (5 Replies)
Discussion started by: vaibhavvsk
5 Replies
lotsfree_pct(5) 						File Formats Manual						   lotsfree_pct(5)

NAME
lotsfree_pct - sets the upper bound before paging daemon starts stealing pages, specified as a percentage of available physical memory VALUES
Default Allowed values Must not be less than (see desfree_pct(5)). DESCRIPTION
is a tunable parameter to set the upper bound before the paging daemon starts stealing pages. It is specified as a percentage of physical memory available after boot. must be a positive integer between 0 and 30 and must be equal to or greater than is the lower bound before paging daemon starts stealing pages (see desfree_pct(5)). The paging daemon in HP-UX acts on a "two hand" model. The daemon runs at least once a second, with one part marking pages of virtual address space as "unused". If the page is referenced before this "aging" hand returns, it will be marked as "used" again. Another section of the daemon, the "steal" hand follows the age hand (the distance between them varies in a well bounded range) and processes pages which are still marked unused, since needed or frequently accessed pages would have a high likelihood of being referenced in the gap between the hands. Exactly how the steal hand treats the pages still marked as unused depends on the comparison of free system physical memory and three pag- ing parameters: and Between and is a periodically re-calculated and, hence, floating threshold known as Thus and are the upper and lower bounds between which moves. is an expression how much the system maintains, in percentage terms (percentage of physical memory available after boot). o If is greater than the system's memory availability is in good shape. The steal hand does nothing as a lot of memory is still available on the system, so there is no need to "steal" a page that might be needed soon. o In the more common case, when is lower than (but higher than the steal hand will begin to steal pages that have remained unreferenced from when the age hand last marked them. "Stealing" a page refers to the process of freeing the page from being allocated for a partic- ular virtual page and making it available for general allocation again. If falls below but still is more than memory availability is still in reasonable shape, but the paging daemon begins stealing pages more aggressively, including putting lower-priority processes to sleep to free up their memory. o When is less than memory availability is getting more critical; and the paging daemon begins deactivating low-priority processes, in other words, swapping out pages to the swap device. Since the exact memory topography varies widely across supported platforms, these three boundary values are tunable to allow for cases where the default values are insufficient, or where the system administrator requires more control over the actions of the paging daemon. In general, however, the automatic calculation performed by default should suffice for most systems. is a system calculated value. Who Is Expected to Change This Tunable? Anyone with super-user privileges. Restrictions on Changing Changes to this tunable take effect immediately. When Should the Value of This Tunable Be Raised? The tunable should only be raised if an administrator feels that the current value provides insufficient free physical memory required by a short lived but critical process. Increasing (and hence to an amout equal to or greater than the amount of physical memory required by this process allows the swapper to move out less frequently used pages from longer running programs, increasing the probability of having the desired amount of memory on hand without waiting for to drop below or during the execution of this critical process. Unless the current is set very low, raising for a process that is not short lived is fairly pointless as will almost certainly drop below and more likely even below thus waking up the swapper and allowing for the physical memory to be freed up over the longer running time as the process requires it. What are the Side Effects of Raising the Value? The swap daemon will begin to steal less-frequently accessed pages from running processes. If large amounts of physical memory is already available without the above situation, this will only slow the already running processes if they need to swap back in their stolen pages. Large amounts of free physical memory without short-lived processes that need it (as mentioned above) is simply a waste. When Should the Value of This Tunable Be Lowered? The tunable should be lowered on systems where swapping is occurring that still have more physical memory available than is needed on aver- age, and that have no sudden sharp peaks in memory usage. What are the Side Effects of Lowering the Value? System swap will occur at a lower memory level. If is set too low (keeping in mind that can never be greater than the system might stall due to memory starvation upon new allocation even though swap space is available. The stall would not be fatal, as the swap daemon run eventually, but will certainly hamper performance. What Other Tunable Values Should Be Changed at the Same Time? should be considered when modifying since Attempting to set above is meaningless and will result in an error. Notes Starting with HP-UX 11iv2, HP recommends the use of to specify the upper bound for the paging daemon. ERROR VALUES
Memory resource management infrastructure is busy. Please try later. Attempting to set above An invalid value is entered that is not an integer between 0 and 30, such as an negative number. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. SEE ALSO
desfree_pct(5). Tunable Kernel Parameters lotsfree_pct(5)
All times are GMT -4. The time now is 08:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy