Re: perfromance impact of vacuum

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jay O'Connor" <joconnor(at)cybermesa(dot)com>
Cc: PostgreSQL List <pgsql-general(at)postgresql(dot)org>
Subject: Re: perfromance impact of vacuum
Date: 2003-07-14 21:15:19
Message-ID: 14243.1058217319@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Jay O'Connor" <joconnor(at)cybermesa(dot)com> writes:
> What impact in performance does vacuum have on an active database?

I've seen varying reports on this; some say it's not a problem, and some
say it is. I suspect (without real proof) that the critical issue is
whether you have adequate I/O bandwidth. If your disk is near
saturation already, the extra I/O load for vacuum can drive you over the
knee of the performance curve and cause serious degradation. But if
you've got spare I/O bandwidth then it's not a big problem.

You can reduce the I/O needs for routine vacuums by only vacuuming the
tables you need to, and selecting an appropriate vacuum frequency for
each one. (You might want to try the "autovacuum" daemon that's being
worked on, as a substitute for doing this tuning by hand. Not sure if
the daemon is ready for prime time though.)

BTW, I suggest moving any followup discussion to pgsql-performance.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Zengfa Gao 2003-07-14 21:28:15 Lock file "/tmp/.s.PGSQL.5432.lock" already exists.
Previous Message Jay O'Connor 2003-07-14 21:13:49 perfromance impact of vacuum