From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Peter Zaitsev <peter@mysql.com>
Cc: linux-kernel@vger.kernel.org, andrea@novell.com,
alexeyk@mysql.com, markw@osdl.org
Subject: Re: IO performance problems with 2.6.9
Date: Fri, 22 Oct 2004 16:54:56 +1000 [thread overview]
Message-ID: <4178AEC0.5050603@yahoo.com.au> (raw)
In-Reply-To: <1098426220.5482.235.camel@sphere.site>
Peter Zaitsev wrote:
> 4) Unrelated but still unfortunate. 2.6.9 kernel seems to behave weird
> if swap is disabled. I was running with 8G of memory allocating 6G for
> MySQL buffers which left about 1.5G for kernel, 1G of which was used
> for file cache. During IO intensive run, using buffered IO I got
> "kswapd" running like a crazy taking 90% of CPU time on one of CPUs.
> What for is it running if there is no swap files enabled ?
>
Can you boot with profile=2, and get a profile of about 30 seconds
while kswapd is going crazy please?
Also capture /proc/vmstat before and after that interaval.
Can you also capture a the output of vmstat 1 while this is happening
Thanks
prev parent reply other threads:[~2004-10-22 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 6:23 Peter Zaitsev
2004-10-22 6:54 ` Nick Piggin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4178AEC0.5050603@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=alexeyk@mysql.com \
--cc=andrea@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markw@osdl.org \
--cc=peter@mysql.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome