Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Seriously, Linux is awesome at memory management and it will give the resources to a process if they are available. Just because it is sitting at 49% does not mean there is a problem. If you look at top do you see any i/o wait or load on the server at all?
Does it look like a load for you? I just tried to perform a memory intense task in my process and memory usage level didn't even move.
That is very strange. I guess, even very demanding tasks on my server don't need more memory, than allocated, or something like that.
But this 49,1. Why such a random number? How did it calculated it to be on 49,1%MEM?
I want to understand from mathematical perspective, why exactly this amount of mem is used.
You can start looking deep into the proc files for the process if you really want to. It's very possible that a big part of that 49.1% is cached dirty memory. So your process may only be using 5-10% but the Linux kernel has not cleaned the rest of that memory and released it as no other apps have requested any memory.
Your top output looks well within optimal ranges, almost perfect.
My advice is don't fix whats not broke, but if you really want to figure it out start hacking into the /proc/ directory and looking at the proc files for that process(not fun at all).