From: "Dr. David Alan Gilbert" <dave@treblig.org>
To: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Cc: linux-kernel mlist <linux-kernel@vger.kernel.org>, nik@linuxbox.cz
Subject: Re: strange values of loadavg and nr of io-blocked tasks
Date: Sat, 17 Nov 2012 14:23:31 +0000 [thread overview]
Message-ID: <20121117142331.GA2868@gallifrey> (raw)
In-Reply-To: <20121116114703.GA8634@pcnci.linuxbox.cz>
* Nikola Ciprich (nikola.ciprich@linuxbox.cz) wrote:
> Hi,
>
> I was doing some I/O tuning of our KVM host, and noticed some
> strange behaviour. When I start some heavy I/O load on guest
> (ie run some fio benchmark), loadavg value of the host jumps
> to value about 65 and holds until load ends. sar reports similar
> number of blocked tasks. I don't really understand those numbers,
> because only active tasks are 4 qemu-kvm threads and few other sleeping
> tasks (so none in R or D state).
> is it possible to somehow find which tasks seem to be blocked?
> or why is loadavg value so high?
> the system is x86_64 quad core with 4GB RAM running centos 6 with 3.0.52-rc1 kernel.
Recebt qemu split there io across multiple threads (as an alternative to AIO),
so what you"ll see is each qemu will dynamically start a load of threads when
is doing heavy IO, none of them will usr much cpu, but each will be blocking on io, and hence count as a 1 for the load.
It does have some flags (which I forget) that let you limit the number of
threads or flip to AIO.
Other than getting a scary loadavg number, it doesn't seem to have any bad
effecta.
Dave
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ gro.gilbert @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
prev parent reply other threads:[~2012-11-17 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 11:47 strange values of loadavg and nr of io-blocked tasks Nikola Ciprich
2012-11-17 14:23 ` Dr. David Alan Gilbert [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=20121117142331.GA2868@gallifrey \
--to=dave@treblig.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nik@linuxbox.cz \
--cc=nikola.ciprich@linuxbox.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.