From: Keir Fraser <keir@xensource.com>
To: Thomas Goirand <thomas@goirand.fr>, xen-devel@lists.xensource.com
Subject: Re: Monitoring I/O rate for each VMs
Date: Mon, 27 Nov 2006 08:12:07 +0000 [thread overview]
Message-ID: <C1904E57.4DA2%keir@xensource.com> (raw)
In-Reply-To: <456A0BD8.8000402@goirand.fr>
On 26/11/06 9:49 pm, "Thomas Goirand" <thomas@goirand.fr> wrote:
> It's nice already, but I'd like to add the I/O rate of each of my VMs as
> well, to know which of them is taking too much bandwidth or hard drives.
> Does one of you know where to get this information?
There are per-vbd read and write stats under
/sys/<path-to-vbd>/statistics/{rd_req,wr_req}
Unfortunately these count requests rather than bytes served. This may be
what you want though, as #requests should be proportional to the number of
expensive disc operations (seeking and settling). Long contiguous requests
are not proportionally more expensive than short ones.
-- Keir
next prev parent reply other threads:[~2006-11-27 8:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-26 21:49 Monitoring I/O rate for each VMs Thomas Goirand
2006-11-27 8:12 ` Keir Fraser [this message]
2006-11-27 9:25 ` Thomas Goirand
2006-11-27 9:41 ` Keir Fraser
2006-11-28 8:04 ` Thomas Goirand
2006-11-28 9:25 ` Muli Ben-Yehuda
2006-11-28 10:51 ` Nick Craig-Wood
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=C1904E57.4DA2%keir@xensource.com \
--to=keir@xensource.com \
--cc=thomas@goirand.fr \
--cc=xen-devel@lists.xensource.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 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.