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 297C65639A for ; Wed, 9 Mar 2005 00:40:06 +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 50750-07 for ; Wed, 9 Mar 2005 00:40:05 +0000 (GMT) Received: from davinci.ethosmedia.com (server227.ethosmedia.com [209.128.84.227]) by svr1.postgresql.org (Postfix) with ESMTP id AC3D35638B for ; Wed, 9 Mar 2005 00:40:03 +0000 (GMT) X-EthosMedia-Virus-Scanned: no infections found 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 7106979 for pgsql-performance@postgresql.org; Tue, 08 Mar 2005 16:41:56 -0800 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: "pgsql-performance@postgresql.org" Subject: Re: Why would writes to pgsql_tmp bottleneck at 1mb/s? Date: Tue, 8 Mar 2005 16:44:32 -0800 User-Agent: KMail/1.7.1 References: <200503081218.24093.josh@agliodbs.com> <200503081617.57190.josh@agliodbs.com> In-Reply-To: <200503081617.57190.josh@agliodbs.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503081644.32497.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.286 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, TO_ADDRESS_EQ_REAL X-Spam-Level: X-Archive-Number: 200503/144 X-Sequence-Number: 10849 Hmmmm..... > > As you can see, we're getting a nice 23mb/s peak for WAL (thanks to > > forcedirectio) and database writes peak at 6mb/s. However, pgsql_tmp, > > which is being used heavily, hovers around 1mb/s, and never goes above > > 1.5mb/s. This seems to be throttling the whole system. > > Never mind, I'm a dork. I accidentally cut the "SET maintenance_work_mem > = 2000000" out of my config file, and it was running with the default 1024K Maybe I'm not an idiot (really!) even with almost 2GB of maintenance_mem, PG still writes to pgsql_tmp no faster than 2MB/s. I think there may be an artificial bottleneck there. Question is, PostgreSQL, OS or hardware? Suggestions? -- --Josh Josh Berkus Aglio Database Solutions San Francisco