From: | tv(at)fuzzy(dot)cz |
---|---|
To: | "AI Rumman" <rummandba(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: 8.2.13 commit is taking too much time |
Date: | 2011-05-10 09:44:46 |
Message-ID: | 53eef814d1a20e20fe059ff7298774f1.squirrel@sq.gransy.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2011-05-10 14:06:38 | Re: Postgres refusing to use >1 core |
Previous Message | Thomas Hägi | 2011-05-10 09:20:34 | Re: indexes ignored when querying the master table |