Results 1 to 2 of 2
Enjoy an ad free experience by logging in. Not a member yet? Register.
How much memory usable to add a new process before paging starts?
Using command like vmstat, free, etc can show RAM used respectively by user apps and by file cache.
My question is: how do I calculate the RAM amount my new process can take before existing executables trigger paging?
I have 1 technique: run a small test program which allocates more and more memory (and often update the pages to ensure those pages are not paged out) and see how the system behaves.
Any other idea?
- Join Date
- May 2008
it depends on amount of RAM you have....
it depends on which Linux kernel you are using and how it is configured specially user space and kernel space.
usually Linux kernel does not provide performance linearly proportional to the size of RAM.
even if you have big RAM, the performance may not be satisfactory due to kernel space issues.
coming to your part, I would say : Linux would behave as you insert the new process and if RAM is not enough definitely paging will happen...
it does not matter whether you allocate test memory memory through test program or your new program.
I am not sure but may be you can try how much memory will be required for your process, specially if there are lots of dynamic memory then its difficult but still static memory you can count...
and see the amount of RAM available to you.....I do not mean increasing the RAM will help but still to some extent it helps a lot.
I think there should be some utility which would tell you the amount of free RAM available currently based on that you may take decision to introduce a new process which involves space of both user space and kernel data structures.