From: Radhakrishnan Manga <Radhakrishnan.Manga@oracle.com>
To: linux-kernel@vger.kernel.org
Subject: vmstat help
Date: Mon, 04 Jun 2001 15:41:49 -0700 [thread overview]
Message-ID: <3B1C0EAD.B0C83157@oracle.com> (raw)
Hi,
I am using the vmstat that came along with the SuSE 7.0 distribution.
I have problem interpretting the data reported by vmstat. The vmstat
document reads that the block information reported is always in terms of
1K blocks. Just to findout the validity of the data reported by vmstat,
I carried out the a small copy test. Here is the configuration I have
1) I have two file systems which are created with 4096 block size
2) These two file systems are on two different disks. (but both are
sitting on same scsi controller)
3) I am trying to copy a 4GB file from one disk to another using the
simple "cp" command.
4) I am capturing vmstat with 30 sec interval. I stop the vmstat after
cp is done
5) The copy takes anywhere between 7 to 10 minutes.
On vmstat report has bi and bo's ranging form 700 to 4000.
Just to get the total blocks read, I multiple the value reported in bi
column with 30 (as 30 sec was my sampling interval) and sum them all. To
my surprise, they add up only to around (1 GB).
What is wrong here, the documentation or my intepretation of vmstat
output.
reply other threads:[~2001-06-04 22:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B1C0EAD.B0C83157@oracle.com \
--to=radhakrishnan.manga@oracle.com \
--cc=linux-kernel@vger.kernel.org \
/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