From: Alexander Staubo <alex@bengler.no>
To: Scott Carey <scott@richrelevance.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Identifying the nature of blocking I/O
Date: Mon, 25 Aug 2008 10:18:24 +0200
Message-ID: <88daf38c0808250118j571bbd98sbade235a141984b4@mail.gmail.com> (raw)
In-Reply-To: <a1ec7d000808241834v48122c83s385a8439253994bc@mail.gmail.com>
References: <20080822115243.GA10981@hyperion.scode.org>
<48B1FD1A.7040807@postnewspapers.com.au>
<a1ec7d000808241834v48122c83s385a8439253994bc@mail.gmail.com>
On Mon, Aug 25, 2008 at 3:34 AM, Scott Carey <scott@richrelevance.com> wrote:
> DTrace is available now on MacOSX, Solaris 10, OpenSolaris, and FreeBSD.
> Linux however is still in the dark ages when it comes to system monitoring,
> especially with I/O.
While that's true, newer 2.6 kernel versions at least have I/O
accounting built in, something which only used to be available through
the "atop" accounting kernel patch:
$ cat /proc/22785/io
rchar: 31928
wchar: 138
syscr: 272
syscw: 4
read_bytes: 0
write_bytes: 0
cancelled_write_bytes: 0
Alexander.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: alex@bengler.no, scott@richrelevance.com
Subject: Re: Identifying the nature of blocking I/O
In-Reply-To: <88daf38c0808250118j571bbd98sbade235a141984b4@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox