Do you run at all before you run out of memory?  Have you tried just starting 
one of the apps at a time and seeing what each seems to do to memory usage?  
Could it be that one of them has a leak?   

I think all the tweaks are really app dependent.  You'll have to measure with 
both a good VM performance monitor and a good java monitor.  
Our largest app finds gencon garbage collection much more efficient (uses more 
than 10% less CPU for them).  Another found that using Async i/o in WAS 
exhibited native memory leak symptoms...  But other than that, we don't have 
specific tweeks that we do for every app.


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 Daniel 
Tate
Sent: Monday, July 26, 2010 3:57 PM
To: [email protected]
Subject: Re: [LINUX-390] OOM Condition on SLES11 running WAS - Tuning problems?

We set swappiness to 0 and started all  servers.  we will see if that helps
and I will look into the sp level upgrade. Does anyone have any good tweeks
for z websphere by chance?

On Jul 26, 2010 4:59 PM, "Marcy Cortes" <[email protected]>
wrote:
> Thanks for that clarification!
>
>
> Marcy
>
> -----Original Message-----
> From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Mark
Post
> Sent: Monday, July 26, 2010 2:21 PM
> To: [email protected]
> Subject: Re: [LINUX-390] OOM Condition on SLES11 running WAS - Tuning
problems?
>
>>>> On 7/26/2010 at 05:05 PM, Marcy Cortes <[email protected]>
wrote:
>> I was going to suggest a dump and a ticket to Novell, but it looks like
you
>> aren't SP1, and so are unsupported.
>
> SLES11 GA is fully supported until 6 months after SP1 went GA. Even after
that, NTS supports the product line throughout its life. We just can't get
Level 3 to look at a problem after 6 months, which means bug fixes won't be
created for a customer unless it's against SP1.
>
>
> Mark Post
>
> ----------------------------------------------------------------------
> 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 more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
> ----------------------------------------------------------------------
> 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 more information on Linux on System z, visit
> http://wiki.linuxvm.org/

----------------------------------------------------------------------
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 more information on Linux on System z, visit
http://wiki.linuxvm.org/

----------------------------------------------------------------------
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 more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to