01-19-2019
Linux uses memory very efficiently, so if you have 32GB of RAM, you are in great shape for most applications. Linux will allocate to active processes and deallocate memory to idle processes as required.
To use "less RAM" as you ask, you need to manage the running processes.
Best is to look at the memory allocated "per process" and not only the "free memory" stats you posted.
Hope this helps.
This User Gave Thanks to Neo For This Post:
10 More Discussions You Might Find Interesting
1. Solaris
Hi All,
I am trying to find the physical memory usage by each process/users.
Can you please let me know how to get the memory usage?.
Thanks,
bsraj. (12 Replies)
Discussion started by: bsrajirs
12 Replies
2. UNIX for Dummies Questions & Answers
Hi Guys,
How can i check the RAM usage for a particular user on the Linux machine.
What command can be used.
Thanks in advance,
Swapna (1 Reply)
Discussion started by: Swapna173
1 Replies
3. Shell Programming and Scripting
Hi i just wanted to know what is the code to display amount of RAM and also the percentage used? I know i can possibly use the vmstat code but what part indicates the RAM? Any help would be much appreciated. Thanks (1 Reply)
Discussion started by: warlock129
1 Replies
4. Linux
Hi
one of our applications that runs on our Linux server leaks memory resulting in Ram that was used by the program not being released back to the operating system once a file has been processed. the result is over a very short period virtual all the memory has been used. an example currently
... (8 Replies)
Discussion started by: treds
8 Replies
5. Solaris
Hi RAM of my system is 24 GB however when i checked the processes pids and counted the memory usage by pmap i found out that the total memory usage is 36 GB
It s obvious that my system might be using some of virtual memory or swap space . How can i check which memory it is using and how ..
... (9 Replies)
Discussion started by: Paarth
9 Replies
6. Red Hat
Hi team
I have three physical servers running on Red Hat Enterprise Linux Server release 6.2 with the following memory conditions:
# cat /proc/meminfo | grep -i mem
MemTotal: 8062888 kB
MemFree: 184540 kB
Shmem: 516 kB
and the following swap conditions:
... (6 Replies)
Discussion started by: hedkandi
6 Replies
7. OS X (Apple)
Hey there! I'm a new user here who registered because I couldn't get these kind of questions answered in the place I directly com from. :o
I've found a discrepancy in total RAM used and I can't figure out why it is. My only guess is there are some RAM used by some stuff impossible to identify,... (2 Replies)
Discussion started by: dasx
2 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I will be creating a process myself and I want to know the average CPU and RAM used by the process over the lifetime of the process. I see that there are various tools available(pidstat) for doing , I was wondering if it possible to do it in a single command while creation.
Thanks in... (3 Replies)
Discussion started by: koustubh
3 Replies
9. UNIX for Beginners Questions & Answers
grpdsku program allows user to check their group disk space in a server environment. The data in the dialog box queries a text file. Each text file is labeled with a current timestamp. Results output to a msgbox. Also, results output to a csv file. The csv file is sent to the user via email
... (13 Replies)
Discussion started by: dellanicholson
13 Replies
10. UNIX for Beginners Questions & Answers
Hello,
I have been running under ubuntu 14.04 trusty and 18.04 bionic.
What I wonder is about:
* how to stop all process in case hdd capacity is almost full and create space for system files
* if possible, to prevent filesystem to write anything into hdd when there is such a risk
* if... (4 Replies)
Discussion started by: baris35
4 Replies
LEARN ABOUT REDHAT
mlockall
MLOCKALL(2) Linux Programmer's Manual MLOCKALL(2)
NAME
mlockall - disable paging for calling process
SYNOPSIS
#include <sys/mman.h>
int mlockall(int flags);
DESCRIPTION
mlockall disables paging for all pages mapped into the address space of the calling process. This includes the pages of the code, data and
stack segment, as well as shared libraries, user space kernel data, shared memory and memory mapped files. All mapped pages are guaranteed
to be resident in RAM when the mlockall system call returns successfully and they are guaranteed to stay in RAM until the pages are
unlocked again by munlock or munlockall 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. For security applications,
only small parts of memory have to be locked, for which mlock is available.
The flags parameter can be constructed from the bitwise OR of the following constants:
MCL_CURRENT Lock all pages which are currently mapped into the address space of the process.
MCL_FUTURE Lock all pages which will become mapped into the address space of the process in the future. These could be for instance new
pages required by a growing heap and stack as well as new memory mapped files or shared memory regions.
If MCL_FUTURE has been specified and the number of locked pages exceeds the upper limit of allowed locked pages, then the system call which
caused the new mapping will fail with ENOMEM. If these new pages have been mapped by the the growing stack, then the kernel will deny
stack expansion and send a SIGSEGV.
Real-time processes should reserve enough locked stack pages before entering the time-critical section, so that no page fault can be caused
by function calls. This can be achieved by calling a function which has a sufficiently large automatic variable and which writes to the
memory occupied by this large array in order to touch these stack pages. This way, enough pages will be mapped for the stack and can be
locked into RAM. The dummy writes ensure that not even copy-on-write page faults can occur in the critical section.
Memory locks do not stack, i.e., pages which have been locked several times by calls to mlockall or mlock will be unlocked by a single call
to 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 mlockall and munlockall are available, _POSIX_MEMLOCK is defined in <unistd.h>.
RETURN VALUE
On success, mlockall returns zero. On error, -1 is returned, errno is set appropriately.
ERRORS
ENOMEM 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 Unknown flags were specified.
CONFORMING TO
POSIX.1b, SVr4. SVr4 documents an additional EAGAIN error code.
SEE ALSO
munlockall(2), mlock(2), munlock(2)
Linux 1.3.43 1995-11-26 MLOCKALL(2)