05 08, Gothenburg Sweden
>>>
>>> Telephone: +46-31-3233569
>>> E-mail: tore.agb...@volvo.com
>>>
>>> http://www.volvo.com/volvoit/global/en-gb/
>>>
>>> -Original Message-
>>> From: Linux on 390 Port [mailto:linux-...@vm.mari
hone: +46-31-3233569
>> E-mail: tore.agb...@volvo.com
>>
>> http://www.volvo.com/volvoit/global/en-gb/
>>
>> -Original Message-----
>> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Shane G
>> Sent: den 28 juli 2010 02:51
>>
390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Shane G
> Sent: den 28 juli 2010 02:51
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: OOM Condition on SLES11 running WAS - Tuning problems?
>
> Hmmm - high "sys" CPU usage, high loadavg, system not talking to anyone.
>
om: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Shane G
Sent: den 28 juli 2010 02:51
To: LINUX-390@VM.MARIST.EDU
Subject: Re: OOM Condition on SLES11 running WAS - Tuning problems?
Hmmm - high "sys" CPU usage, high loadavg, system not talking to anyone.
Smells like
Daniel Tate wrote:
Unfortunately it did not. It continued to grow and grow until oom
killed in a loop. We're supposed to have a max size of 512MB per VM.
A max heap of 512 MB per VM doesn't mean that each VM will only use
512M, it means that it will grow to 512M + any extra memory required by
mail: tore.agb...@volvo.com
http://www.volvo.com/volvoit/global/en-gb/
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Daniel
Tate
Sent: den 27 juli 2010 21:30
To: LINUX-390@VM.MARIST.EDU
Subject: Re: OOM Condition on SLES11 running WAS - Tuning prob
Behalf Of Daniel
Tate
Sent: den 27 juli 2010 16:53
To: LINUX-390@VM.MARIST.EDU
Subject: Re: OOM Condition on SLES11 running WAS - Tuning problems?
Yes, but no memory ever gets freed. The system stops responding and
is too busy dumping information to the console screen to respond to
anything at the c
t;
> Marcy
>
> -Original Message-
> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark
Post
> Sent: Monday, July 26, 2010 2:21 PM
> To: LINUX-390@vm.marist.edu
> Subject: Re: [LINUX-390] OOM Condition on SLES11 running WAS - Tuning
problems?
>
>
Hmmm - high "sys" CPU usage, high loadavg, system not talking to anyone.
Smells like it's busy doing its own stuff. If it were me I'd want to know
trends for things like
swap-in and swap-out rates, tasks in uninterruptible sleep, context switch
counts.
SAR is too granular to be any use even if
On Behalf Of Daniel
Tate
Sent: Tuesday, July 27, 2010 12:30 PM
To: LINUX-390@vm.marist.edu
Subject: Re: [LINUX-390] OOM Condition on SLES11 running WAS - Tuning problems?
Unfortunately it did not. It continued to grow and grow until oom
killed in a loop. We're supposed to have a max size of
-
> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Daniel
> Tate
> Sent: Tuesday, July 27, 2010 7:53 AM
> To: LINUX-390@vm.marist.edu
> Subject: Re: [LINUX-390] OOM Condition on SLES11 running WAS - Tuning
> problems?
>
> Yes, but no memory ever gets free
..@vm.marist.edu] On Behalf Of Daniel
Tate
Sent: Tuesday, July 27, 2010 7:53 AM
To: LINUX-390@vm.marist.edu
Subject: Re: [LINUX-390] OOM Condition on SLES11 running WAS - Tuning problems?
Yes, but no memory ever gets freed. The system stops responding and
is too busy dumping information to th
Yes, but no memory ever gets freed. The system stops responding and
is too busy dumping information to the console screen to respond to
anything at the console or network.
And a system-wide panic would provide me with a core file to analyze
and send off; though the progress we've made thanks to t
On Mon, 26 Jul 2010 10:24:06 -0500, Daniel Tate
wrote:
> At this point i see two problems:
>
> 1) Why is OOM Kill not functioning properly
> 2) Why is websphere performance so awful?
If you run WAS (or any Java app) in swap, performance will be terrible, as
a rule of thumb; if you've got 16GB al
Some more info please.
... you get a OOM condition ?.
... the/a large consumer gets killed ?
... the system "halts" (explain) ?.
You *want* a system-wide panic ?. If so, setting /proc/sys/vm/panic_on_oom to
"1" will
have the desired effect on non zLinux.
Shane ...
On Tue, Jul 27th, 2010 at 1:2
sage 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:linux-...
---
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Daniel
Tate
Sent: Monday, July 26, 2010 8:24 AM
To: LINUX-390@vm.marist.edu
Subject: [LINUX-390] OOM Condition on SLES11 running WAS - Tuning problems?
We're running websphere on a z9 under z/VM 4 systems are live out o
:57 PM
To: LINUX-390@vm.marist.edu
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
;
> -Original Message-
> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark
Post
> Sent: Monday, July 26, 2010 2:21 PM
> To: LINUX-390@vm.marist.edu
> Subject: Re: [LINUX-390] OOM Condition on SLES11 running WAS - Tuning
problems?
>
>>>>
Thanks for that clarification!
Marcy
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post
Sent: Monday, July 26, 2010 2:21 PM
To: LINUX-390@vm.marist.edu
Subject: Re: [LINUX-390] OOM Condition on SLES11 running WAS - Tuning problems
>>> On 7/26/2010 at 05:05 PM, Marcy Cortes
>>> 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 i
--Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Daniel
Tate
Sent: Monday, July 26, 2010 11:28 AM
To: LINUX-390@vm.marist.edu
Subject: Re: [LINUX-390] OOM Condition on SLES11 running WAS - Tuning problems?
Yeah, i saw that.. problem is these same apps run on 1
Set swappiness to 0. Can you just start 1 node as a test?
Ray
> -Original Message-
> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On
> Behalf Of Daniel Tate
> Sent: Monday, July 26, 2010 2:28 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: OOM Condition on
Thank you for your cooperation."
>
>
> -Original Message-
> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
> Daniel Tate
> Sent: Monday, July 26, 2010 8:24 AM
> To: LINUX-390@vm.marist.edu
> Subject: [LINUX-390] OOM Condition on SLES11 r
elete this message. Thank you for
your cooperation."
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Daniel
Tate
Sent: Monday, July 26, 2010 8:24 AM
To: LINUX-390@vm.marist.edu
Subject: [LINUX-390] OOM Condition on SLES11 running WAS - Tuning p
We're running websphere on a z9 under z/VM 4 systems are live out of 8. it
is running apps that consume around 16GB of memory on a Windows machine. on
this, we have allocated 10G of real storage (RAM) and around 35GB of
Swap.When websphere starts, it consumes all the memory eventually and
ha
26 matches
Mail list logo
