From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Carey <scott@richrelevance.com>
Cc: Craig Ringer <craig@postnewspapers.com.au>
Cc: Peter Schuller <peter.schuller@infidyne.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Identifying the nature of blocking I/O
Date: Sun, 24 Aug 2008 21:49:51 -0400
Message-ID: <1028.1219628991@sss.pgh.pa.us> (raw)
In-Reply-To: <a1ec7d000808241834v48122c83s385a8439253994bc@mail.gmail.com>
References: <20080822115243.GA10981@hyperion.scode.org>
<48B1FD1A.7040807@postnewspapers.com.au>
<a1ec7d000808241834v48122c83s385a8439253994bc@mail.gmail.com>
"Scott Carey" <scott@richrelevance.com> writes:
> 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.
Oh, after poking around a bit, I should note that some of my Red Hat
compatriots think that "systemtap" is the long-term Linux answer here.
I know zip about it myself, but it's something to read up on if you are
looking for better performance monitoring on Linux.
regards, tom lane
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: tgl@sss.pgh.pa.us, scott@richrelevance.com, craig@postnewspapers.com.au, peter.schuller@infidyne.com
Subject: Re: Identifying the nature of blocking I/O
In-Reply-To: <1028.1219628991@sss.pgh.pa.us>
* 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