We found that with the default vm.swapiness setting of 60, our biggest production WAS app would slowly fill up all of his swap space, run out after 5 days or so, and crash. Setting it to 20 made that problem go away . With 20, it doesn't even creep up at all, or even use much if any. Why this happened has yet to be explained (and we had problems opened with both IBM and Novell), but because of that, we are leaving it to 20 as the default on all server builds.
Seems like 60=bug to me, but oh well! We're happy at 20. Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Ayer, Paul W Sent: Wednesday, April 01, 2009 12:20 PM To: [email protected] Subject: [LINUX-390] swappiness & drop_caches ? Good afternoon all, Just wondering if anyone has some input (good, bad, warnings ...) or has had to used the following two items .... we are running VM5.4 and RHEL4.x and 5.x sles 9 and 10 systems 1) Setting swappiness to other than the default of 60 ? Echo nn > /proc/sys/vm/swappiness 2) dropping caches ? Echo 1 or 2 or 3 > /proc/sys/vm/drop_caches Thanks, Paul ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
