From: | Peter van Hardenberg <pvh(at)pvh(dot)ca> |
---|---|
To: | Alessandro Gagliardi <alessandro(at)path(dot)com> |
Cc: | Steve Crawford <scrawford(at)pinpointresearch(dot)com>, Andy Colson <andy(at)squeakycode(dot)net>, Thom Brown <thom(at)linux(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: set autovacuum=off |
Date: | 2012-02-23 18:42:05 |
Message-ID: | CAAcg=kXAGaH-U8RVTDDwxpnmYLSXfg2NxO1Ns9pAgXjctnEs-g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, Feb 23, 2012 at 10:38 AM, Alessandro Gagliardi
<alessandro(at)path(dot)com> wrote:
> On Thu, Feb 23, 2012 at 10:01 AM, Steve Crawford
> <scrawford(at)pinpointresearch(dot)com> wrote:
> So if it's not auto-vacuuming that's making my inserts so slow, what is it?
> I'm batching my inserts (that didn't seem to help at all actually, but maybe
> cause I had already turned off synchronous_commit anyway). I've gotten rid
> of a bunch of indices (especially those with low cardinality–that I did
> around the same time as disabling auto-vacuum, so that could account for the
> coincidental speed up). I'm not sure what else I could be doing wrong. It's
> definitely better than it was a few days ago, but I still see "LOG:
> duration: 77.315 ms statement: COMMIT" every minute or two.
>
Have you considered that you may have lock contention? Sampling
pg_locks may be illuminating; based on your description the lock
contention would be intermittent, so I wouldn't trust an n=1 test.
-p
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt." -- Kurt Vonnegut
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-02-23 19:04:34 | Re: Very long deletion time on a 200 GB database |
Previous Message | Alessandro Gagliardi | 2012-02-23 18:38:29 | Re: set autovacuum=off |