| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Mindaugas Riauba <mind(at)bi(dot)lt>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Degrading performance |
| Date: | 2003-06-02 16:34:43 |
| Message-ID: | Pine.LNX.4.33.0306021034190.11997-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, 2 Jun 2003, Tom Lane wrote:
> "Mindaugas Riauba" <mind(at)bi(dot)lt> writes:
> > I have table with slowly degrading performance. Table is special is
> > such way that all its rows are updated every 5 minutes (routers interfaces).
> > vacuum does not help. vacuum full does but I'd like to avoid it.
>
> VACUUM will do the trick, you just need to do it every five minutes or
> so. I suggest a cron job to vacuum just the one table.
>
> > INFO: Rel ifdata: Pages: 4887 --> 17; Tuple(s) moved: 776.
> > CPU 0.30s/0.35u sec elapsed 1.65 sec.
>
> That says you waited way too long to vacuum --- over two hundred update
> cycles, evidently.
Don't forget to crank up your fsm settings in $PGDATA/postgresql.conf as
well.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-06-02 17:25:22 | Re: Degrading performance |
| Previous Message | scott.marlowe | 2003-06-02 15:23:11 | Re: Enabling and Disabling Sequencial Scan |