From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Lonni J Friedman <netllama(at)gmail(dot)com> |
Cc: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>, Andy Colson <andy(at)squeakycode(dot)net>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Re: significant performance hit whenever autovacuum runs after upgrading from 9.0 -> 9.1 |
Date: | 2012-05-24 19:34:13 |
Message-ID: | 28785.1337888053@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Lonni J Friedman <netllama(at)gmail(dot)com> writes:
> No, not lots of subqueries or ORDERing, and most queries only touch a
> single table. However, I'm honestly not sure that I'm following where
> you're going with this. The problem isn't triggered by explicit
> queries. I can disable all external access, and simply wait for
> autovacuum to kick off, and the box starts to die.
Can you correlate the performance hit with any specific part of
autovacuum? In particular, I'm wondering if it matters whether vacuum
is cleaning tables or indexes --- it alternates between the two, and the
access patterns are a bit different. You could probably watch what the
autovac process is doing with strace to see what it's accessing.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Lonni J Friedman | 2012-05-24 19:37:37 | Re: Re: significant performance hit whenever autovacuum runs after upgrading from 9.0 -> 9.1 |
Previous Message | Lonni J Friedman | 2012-05-24 19:28:14 | Re: Re: significant performance hit whenever autovacuum runs after upgrading from 9.0 -> 9.1 |