X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6CF443A25AF for ; Tue, 4 Jan 2005 21:34:09 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 42311-01 for ; Tue, 4 Jan 2005 21:33:47 +0000 (GMT) Received: from davinci.ethosmedia.com (server226.ethosmedia.com [209.128.84.226]) by svr1.postgresql.org (Postfix) with ESMTP id AC2D23A3F79 for ; Tue, 4 Jan 2005 21:33:48 +0000 (GMT) Received: from [64.81.245.111] (account josh@agliodbs.com HELO temoku.sf.agliodbs.com) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 6865575; Tue, 04 Jan 2005 13:35:26 -0800 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Rod Taylor Subject: Re: query rewrite using materialized views Date: Tue, 4 Jan 2005 13:37:27 -0800 User-Agent: KMail/1.7.1 Cc: "Wager, Ryan D [NTK]" , Postgresql Performance References: <8543375597A43D4D8388D75ACD32B9B301F72C1A@PDAWB06C.ad.sprint.com> <1104868462.37702.114.camel@home> In-Reply-To: <1104868462.37702.114.camel@home> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501041337.27884.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.042 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/47 X-Sequence-Number: 9737 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