Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id B9E1763254B for ; Wed, 9 Jun 2010 04:10:03 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 42590-06 for ; Wed, 9 Jun 2010 07:09:54 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mail.postgresql.org (Postfix) with ESMTP id E0C956321B1 for ; Wed, 9 Jun 2010 04:09:53 -0300 (ADT) Received: from [192.168.1.6] (pool-96-244-14-10.bltmmd.fios.verizon.net [96.244.14.10]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0MPIp6-1OQd8q08nI-004PfJ; Wed, 09 Jun 2010 09:09:52 +0200 Message-ID: <4C0F3E3E.6050805@2ndquadrant.com> Date: Wed, 09 Jun 2010 03:09:50 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Thomas Kellerer CC: pgsql-admin@postgresql.org Subject: Re: Details about pg_stat_bgwriter References: <4C0E7E3E.2070309@2ndquadrant.com> <4C0F2339.8070403@2ndquadrant.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX19RBEV8n3lxklIEEhoA3ezAZ10wlPvDXXNOlaE GgiemHlj9Vexwg9TNC2X/nYisjoGHZinFWIvwkJptotD6L4bUl bHJDShc6eI1ipi49kTsYZlEj0Z6wslK X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.8 tagged_above=-10 required=5 tests=BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201006/82 X-Sequence-Number: 34860 Thomas Kellerer wrote: > I don't think we have a caching issue though, it's just one (regular) > bulk import that does some heavy writes which we need to tune. Read > performance is absolutely fine, but everything around vacuum and > checkpointing seems to slow down the import massively. > So would taking a snapshot before and after this import be the right > way to start the analysis? Sure. Might want to grab one at those two points, then at a point right before the next big import happens, so that you have what a relatively idle period looks like for comparison sake. -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us