Like Dave says, this is where you need the tools becaues your mileage may definitely vary.
Our big app has 1G on it's HTTP servers (3 - one on each LPAR). I see at the moment it's got 360M in cache, so probably could be trimmed a some - but it did crash at 750M due to running out of storage. It runs 4 instances of IHS and support peristent connections and SSL to other machines out there... So measure! Don't crash! Marcy Cortes "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 David Boyes Sent: Friday, March 16, 2007 7:52 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Sizing an HTTP-server guest > A customer has one defined at 96M, no swap. That's consistent with what we're seeing as well. One site we deal with has the guests running only the HTTP server defined as 96M w/16M VDISK swap with good performance. ---------------------------------------------------------------------- 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
