Well, our experience has been it depends. Depends on the number of apps,
and the number of app servers per node. JVM heap size for the App Server
(and dep. mgr and node agent if you are in Network Deployment mode)
with 4-5 apps deployed on 2 servers with a JVM heap of 128 and 230 megs,
respectively for the servers, we're running into some memory pressure at
1.2 gigs. Probably gonan go 1.3 shortly
Again, your milage may vary. We eliminated one server on a test box when
the application that had required a seperate server was re-tuned to play
nice with other apps in the server.
With the second server perm. gone, it looks like we could get away with 1
gig, for our current application load.
"Seader, Cameron"
<[EMAIL PROTECTED]
er.com> To
Sent by: Linux on [EMAIL PROTECTED]
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: VMware vs. VM
12/10/2004 01:05
PM
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
Does anyone have any pointers on how much real memory and swap should be
allocated to a linux guest for Websphere applications. We are running 500
mb real memory and about 1.1GB of swap.
-Cameron
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Richard Troth
Sent: Friday, December 10, 2004 11:59
To: [EMAIL PROTECTED]
Subject: Re: VMware vs. VM
Hi, Doug, ...
Wow! You've gotten some great responses already.
Clearly, you need to think about your workload before anything else.
You don't want to say "z/VM is better" and then throw a virus-scanning
e-mail service on it and watch the thing tank because of CPU load.
* the INTeL (and copycat) chip doesn't virtualize itself
as well as the zSeries processor, so you get what I call
higher "insertion loss", more of a hit relative to native
performance when running PC software in a virtual machine
* z/VM scales up better than VMware
(probably related to the first point)
* VMware controls are GUI oriented
(but they do now have some early automation tools)
* z/VM is HIGHLY automatable, configurable, and customizable
but is (3270 and EBCDIC) really foreign to Windows people
Cameron's report will be interesting, if they can share that.
And what Adam and others have said is right on.
Let me also play the opportunist and mention FreeVM-L.
It is a LISTSERV discussion list for talking about things like this.
Originally, the "free" part of the name was to indicate the goal
of having an open standard for describing virtual machines, and that's
still the central point of the list. But questions like yours
are also the kind of thing we want to deal with there.
Subscribe at your nearest LISTSERV.
-- R;
----------------------------------------------------------------------
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
This transmission may contain information that is privileged, confidential
and/or exempt from disclosure under applicable law. If you are not the
intended recipient, you are hereby notified that any disclosure, copying,
distribution, or use of the information contained herein (including any
reliance thereon) is STRICTLY PROHIBITED. If you received this transmission
in error, please immediately contact the sender and destroy the material in
its entirety, whether in electronic or hard copy format. Thank you. A1.
----------------------------------------------------------------------
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
