Quote:
Originally Posted by jackd1000
The constant high rate of swap usage would suggest to me that the algorithm is wanting to do something like swap out aged/inactive processes all the time.
|
The constant high swap space usage indicates you don't have enough swap space.
Linux does not swap out inactive processes, it swaps out inactive anonymous pages from processes, regardless of whether the processes are active or inactive.
Many server processes uses significant anonymous memory during startup that is then untouched until the process shuts down. Those pages should be swapped out.
If that is typical, you have no problem. The key number is kbcached. That remained above half your total memory for that whole set of stats. With kbcached that high, the performance improvement from increasing swap size would be too tiny to measure.
With some very unusual memory allocation patterns by processes, it is possible that those processes could fail due to lack of swap space even with kbcached that high, but it is extremely unlikely.
I would allocate more swap space anyway. I really hate to see swap mostly used in normal operation. But there may not be a serious need to allocate more swap.
Quote:
|
My memory usage varies between 70%and 99% daily
|
That is far less significant than you think. 99% memory use is fine as long as cache is the major user of memory. Read this:
http://www.linuxatemyram.com/
Quote:
Originally Posted by jackd1000
Is there any risk in creating a swap file on a software raid device (/dev/md0) ? I assume that when looking at /etc/fstab on reboot, Linux will resolve all filesystems before invoking the use of a swap file ?
|
Lots of people allocate swap files on software RAID devices. I've never done so myself, so I don't know exactly what you need in /etc/fstab and other startup files to get everything to happen in the correct sequence. I still wouldn't really call that a "risk". If things happen in the wrong sequence on startup the extra swap space simply won't get added. That is no worse than not having it set up in the first place.
Just remember after the next reboot to check to see if your extra swap space was added properly during startup. If not, you can manually add it, try fixing whatever the startup sequence issue might be and check it again the time after that.