From: Ron Mayer <ron@intervideo.com>
To: Josh Berkus <josh@agliodbs.com>
To: Pgsql-performance@postgresql.org
Cc: ron@intervideo.com
Subject: Re: Performance on large data transformations
Date: Mon, 17 Mar 2003 12:06:39 -0800
Message-ID: <POEDIPIPKGJJLDNIEMBECEGHCGAA.ron@intervideo.com> (raw)
In-Reply-To: <200303170938.38365.josh@agliodbs.com>
Josh Berkus wrote:
>
>There is, for that matter, no kernel swap activity, but I'm not
>sure how to measure Postgres temp file activity.
Of course you could:
mv /wherever/data/base/16556/pgsql_tmp /some_other_disk/
ln -s /some_other_disk/pgsql_tmp /wherever/data/base/16556
and use "iostat" from the "systat" package to watch how much you're
using the disk the temp directory's on.
In fact, for OLAP stuff I've had this help performance because
quite a few data warehousing operations look like:
First read from main database,
do a big hash-or-sort, (which gets written to pgsql_tmp),
then read from this temporary table and write result to main database
PS: Yes, I know this doesn't help the FSM stuff you asked about.
Ron
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: ron@intervideo.com, josh@agliodbs.com
Subject: Re: Performance on large data transformations
In-Reply-To: <POEDIPIPKGJJLDNIEMBECEGHCGAA.ron@intervideo.com>
References: <200303170938.38365.josh@agliodbs.com> <POEDIPIPKGJJLDNIEMBECEGHCGAA.ron@intervideo.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