mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "List User" <lists@chaven.com>
To: "Chris Evans" <chris@scary.beasts.org>, <Tony.Young@ir.com>
Cc: <chris@scary.beasts.org>, <slug@slug.org.au>, <csa@oss.sgi.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Linux Disk Performance/File IO per process
Date: Mon, 29 Jan 2001 16:41:18 -0600	[thread overview]
Message-ID: <037d01c08a44$9bb9ace0$160912ac@stcostlnds2zxj> (raw)
In-Reply-To: <Pine.LNX.4.30.0101291209290.3063-100000@ferret.lmh.ox.ac.uk>

Just wanted to 'chime' in here.  Yes this would be noisy and will have an
affect
on system performance however these statistics are what are used in
conjunction with
several others to size systems as well as to plan on growth.  If Linux is to
be put into
an enterprise environment these types of statistics will be needed.

When you start hooking up 100's of 'physical volumes' (be it real disks or
raided logical drives)
this data helps you pin-point problems.   I think the idea of having the
ability to turn such accounting
on/off via  /proc entry a very nice method of doing things.

That way you can leave it off for normal run-time but when users complain or
DBA's et al
you can turn it on get some stats for a couple hours/days whatever, then
turn it back off and
plan an upgrade or re-create a logical volume or stripping set.


Steve
----- Original Message -----
From: "Chris Evans" <chris@scary.beasts.org>
To: <Tony.Young@ir.com>
Cc: <chris@scary.beasts.org>; <slug@slug.org.au>; <csa@oss.sgi.com>;
<linux-kernel@vger.kernel.org>
Sent: Monday, January 29, 2001 07:26
Subject: RE: Linux Disk Performance/File IO per process


>
> On Mon, 29 Jan 2001 Tony.Young@ir.com wrote:
>
> > Thanks to both Jens and Chris - this provides the information I need to
> > obtain our busy rate
> > It's unfortunate that the kernel needs to be patched to provide this
> > information - hopefully it will become part of the kernel soon.
> >
> > I had a response saying that this shouldn't become part of the kernel
due to
> > the performance cost that obtaining such data will involve. I agree that
a
> > cost is involved here, however I think it's up to the user to decide
which
> > cost is more expensive to them - getting the data, or not being able to
see
> > how busy their disks are. My feeling here is that this support could be
user
> > configurable at run time - eg 'cat 1 > /proc/getdiskperf'.
>
> Hi,
>
> I disagree with this runtime variable. It is unnecessary complexity.
> Maintaining a few counts is total noise compared with the time I/O takes.
>
> Cheers
> Chris
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-29 22:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-29  2:50 Tony.Young
2001-01-29 13:26 ` Chris Evans
2001-01-29 22:41   ` List User [this message]
2001-01-30  2:18     ` James Sutherland
2001-01-30  2:49       ` List User
  -- strict thread matches above, loose matches on Subject: below --
2001-01-29  1:54 Tony.Young
2001-01-29  2:02 ` Jens Axboe
2001-01-29  2:04 ` Chris Evans
2001-01-29 15:39   ` Szabolcs Szakacsits
2001-01-29 18:27     ` Mike Galbraith

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='037d01c08a44$9bb9ace0$160912ac@stcostlnds2zxj' \
    --to=lists@chaven.com \
    --cc=Tony.Young@ir.com \
    --cc=chris@scary.beasts.org \
    --cc=csa@oss.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=slug@slug.org.au \
    /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

all inboxes | Powered by JetHome®