From: Greg Smith <greg@2ndquadrant.com>
To: Thomas Kellerer <spam_eater@gmx.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: Details about pg_stat_bgwriter
Date: Wed, 09 Jun 2010 03:09:50 -0400
Message-ID: <4C0F3E3E.6050805@2ndquadrant.com> (raw)
In-Reply-To: <hune6p$2fm$1@dough.gmane.org>
References: <hulnta$mqe$1@dough.gmane.org>
<4C0E7E3E.2070309@2ndquadrant.com>
<4C0F2339.8070403@2ndquadrant.com>
<hune6p$2fm$1@dough.gmane.org>
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
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-admin@postgresql.org
Cc: greg@2ndquadrant.com, spam_eater@gmx.net
Subject: Re: Details about pg_stat_bgwriter
In-Reply-To: <4C0F3E3E.6050805@2ndquadrant.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