From: Josh Berkus <josh@agliodbs.com>
To: Rod Taylor <pg@rbt.ca>
Cc: Wager, Ryan D [NTK] <Ryan.D.Wager@mail.sprint.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: query rewrite using materialized views
Date: Tue, 4 Jan 2005 13:37:27 -0800
Message-ID: <200501041337.27884.josh@agliodbs.com> (raw)
In-Reply-To: <1104868462.37702.114.camel@home>
References: <8543375597A43D4D8388D75ACD32B9B301F72C1A@PDAWB06C.ad.sprint.com>
<1104868462.37702.114.camel@home>
Ryan,
> > I do this, PG gets forked many times, it is tough to find the max
> > number of times I can do this, but I have a Proc::Queue Manager Perl
> > driver that handles all of the copy calls. I have a quad CPU machine.
> > Each COPY only hits ones CPU for like 2.1% but anything over about 5
> > kicks the load avg up.
That's consistent with Xeon problems we've seen elsewhere. Keep the # of
processes at or below the # of processors.
Moving pg_xlog is accomplished through:
1) in 8.0, changes to postgresql.conf
(in 8.0 you'd also want to explore using multiple arrays with tablespaces to
make things even faster)
2) in other versions:
a) mount a seperate disk on PGDATA/pg_xlog, or
b) symlink PGDATA/pg_xlog to another location
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, pg@rbt.ca, Ryan.D.Wager@mail.sprint.com
Subject: Re: query rewrite using materialized views
In-Reply-To: <200501041337.27884.josh@agliodbs.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