Skip site navigation (1) Skip section navigation (2)

Re: Identifying the nature of blocking I/O

From: "Alexander Staubo" <alex(at)bengler(dot)no>
To: "Scott Carey" <scott(at)richrelevance(dot)com>
Cc: pgsql-performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Identifying the nature of blocking I/O
Date: 2008-08-25 08:18:24
Message-ID: 88daf38c0808250118j571bbd98sbade235a141984b4@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Mon, Aug 25, 2008 at 3:34 AM, Scott Carey <scott(at)richrelevance(dot)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.

In response to

Responses

pgsql-performance by date

Next:From: RWDate: 2008-08-25 08:32:24
Subject: Re: Identifying the nature of blocking I/O
Previous:From: Tino WildenhainDate: 2008-08-25 06:01:47
Subject: Re: NOW vs CURRENT_DATE

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group