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
MLOCK(2)						     Linux Programmer's Manual							  MLOCK(2)

NAME
mlock - disable paging for some parts of memory SYNOPSIS
#include <sys/mman.h> int mlock(const void *addr, size_t len); DESCRIPTION
mlock disables paging for the memory in the range starting at addr with length len bytes. All pages which contain a part of the specified memory range are guaranteed be resident in RAM when the mlock system call returns successfully and they are guaranteed to stay in RAM until the pages are unlocked by munlock or munlockall, until the pages are unmapped via munmap, or until the process terminates or starts another program with exec. Child processes do not inherit page locks across a fork. Memory locking has two main applications: real-time algorithms and high-security data processing. Real-time applications require determin- istic timing, and, like scheduling, paging is one major cause of unexpected program execution delays. Real-time applications will usually also switch to a real-time scheduler with sched_setscheduler. Cryptographic security software often handles critical bytes like passwords or secret keys as data structures. As a result of paging, these secrets could be transfered onto a persistent swap store medium, where they might be accessible to the enemy long after the security software has erased the secrets in RAM and terminated. Memory locks do not stack, i.e., pages which have been locked several times by calls to mlock or mlockall will be unlocked by a single call to munlock for the corresponding range or by munlockall. Pages which are mapped to several locations or by several processes stay locked into RAM as long as they are locked at least at one location or by at least one process. On POSIX systems on which mlock and munlock are available, _POSIX_MEMLOCK_RANGE is defined in <unistd.h> and the value PAGESIZE from <lim- its.h> indicates the number of bytes per page. NOTES
With the Linux system call, addr is automatically rounded down to the nearest page boundary. However, POSIX 1003.1-2001 allows an imple- mentation to require that addr is page aligned, so portable applications should ensure this. RETURN VALUE
On success, mlock returns zero. On error, -1 is returned, errno is set appropriately, and no changes are made to any locks in the address space of the process. ERRORS
ENOMEM Some of the specified address range does not correspond to mapped pages in the address space of the process or the process tried to exceed the maximum number of allowed locked pages. EPERM The calling process does not have appropriate privileges. Only root processes are allowed to lock pages. EINVAL len was not a positive number. CONFORMING TO
POSIX.1b, SVr4. SVr4 documents an additional EAGAIN error code. SEE ALSO
mlockall(2), munlock(2), munlockall(2), munmap(2), setrlimit(2) Linux 1.3.43 1995-11-26 MLOCK(2)
All times are GMT -4. The time now is 03:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy