From: tv@fuzzy.cz
To: AI Rumman <rummandba@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: 8.2.13 commit is taking too much time
Date: Tue, 10 May 2011 11:44:46 +0200
Message-ID: <53eef814d1a20e20fe059ff7298774f1.squirrel@sq.gransy.com> (raw)
In-Reply-To: <BANLkTimRRj1KX5YXWyjcc9wQZJuEMgxAsA@mail.gmail.com>
References: <BANLkTimRRj1KX5YXWyjcc9wQZJuEMgxAsA@mail.gmail.com>
> Any idea how to improve the performance?
Hmmm, I guess we'll need more info about resource usage (CPU, I/O, locks)
used when the commit happens. Run these two commands
$ iostat -x 1
$ vmstat 1
and then execute the commit. See what's causing problems. Is the drive
utilization close to 100%? You've problems with disks (I'd bet this is the
cause). Etc.
There's a very nice chapter about this in Greg's book.
BTW what filesystem are you using? Ext3, ext4, reiserfs, xfs? I do
remember there were some problems with sync, that some filesystems are
unable to sync individual files and always sync everything (which is going
to suck if you want to sync just the WAL).
regards
Tomas
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: tv@fuzzy.cz, rummandba@gmail.com
Subject: Re: 8.2.13 commit is taking too much time
In-Reply-To: <53eef814d1a20e20fe059ff7298774f1.squirrel@sq.gransy.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