I realize that it would not be a apples to apples comparison, but is there a similar discussion about sizing guests that are running DB2? With STMM on? And the "Be ware!"s? Does DB2 have instrumentation that can tell you how it's using memory and indicate "good" value. I am aware the STMM is suppose to do that automatically, but I am suspicious of it's assumption since it does know account for running under zVM. Thx
Rob van der Heij <rvdh...@velocitysoftware.com> Sent by: Linux on 390 Port <LINUX-390@VM.MARIST.EDU> 02/05/2010 06:14 AM Please respond to Linux on 390 Port <LINUX-390@VM.MARIST.EDU> To LINUX-390@VM.MARIST.EDU cc Subject Re: A Question on Sizing z/VM Linux Guests 2010/2/4 van Sleeuwen, Berry <berry.vansleeu...@atosorigin.com>: > We have some oracle guests that have been set to 1G. And they actually > need only 300M. The rest is occupied in cache (between 650 and 710M). Be aware! The Oracle SGA lives in Linux page cache, together with in-use programs and shared libraries. So on Oracle systems it is normal to see a large page cache and it is not all waste. The Oracle instrumentation can tell you how much of the allowed SGA size is actually being use (and whether that is enough). When the system sees enough data, it will eventually grow to use all allowed SGA space. Without access to those metrics, you could write a "1" into the /proc/sys/vm/drop_caches to have Linux drop all other stuff from page cache. You will see Linux reclaim some of that in a few minutes, and that might be a good stake in the ground. > I'd like to decrease the machines but it is quite hard to convince the > oracle group that the machines do not need the memory. Instead, they > even want to increase to 2G because the books tell them to. While the > documents suggest the oracle will benefit from the increased memory, in > reality VM will page more and the effect is an overall decrease in > performance for all guests. You're correct that there is a cost for increasing the virtual machine size, but there is also a cost for not increasing it. You need to measure and analyze that. And you have the product that that can help you understand the cost rather than tune by fear and doubt :-) There's always a trade-off and your analysis should include the utilization of the virtual machine. When the server is rarely active, it may be acceptable when it is less efficient since that reduces the resource cost when it is idle. But servers that are very busy will benefit from efficient operation and you're less concerned about the idle footprint. > I would suggest to keep the guest as small as possible. Also try to > limit SGA and such. Among the "such" is also the PGA as sized by the DBA. That does not live in page cache but in anonymous memory in Linux (the "used" part that is not cache). Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ----------------------------------------- Please consider the environment before printing this email and any attachments. This e-mail and any attachments are intended only for the individual or company to which it is addressed and may contain information which is privileged, confidential and prohibited from disclosure or unauthorized use under applicable law. If you are not the intended recipient of this e-mail, you are hereby notified that any use, dissemination, or copying of this e-mail or the information contained in this e-mail is strictly prohibited by the sender. If you have received this transmission in error, please return the material received to the sender and delete all copies from your system. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
