Re: Identifying the nature of blocking I/O - Mailing list pgsql-performance

From Alexander Staubo
Subject Re: Identifying the nature of blocking I/O
Date
Msg-id 88daf38c0808250118j571bbd98sbade235a141984b4@mail.gmail.com
Whole thread Raw
In response to Re: Identifying the nature of blocking I/O  ("Scott Carey" <scott@richrelevance.com>)
Responses Re: Identifying the nature of blocking I/O  (RW <postgres@tauceti.net>)
List pgsql-performance
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.

pgsql-performance by date:

Previous
From: Tino Wildenhain
Date:
Subject: Re: NOW vs CURRENT_DATE
Next
From: RW
Date:
Subject: Re: Identifying the nature of blocking I/O