From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Peter Bauer" <peter(dot)m(dot)bauer(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Overload after some minutes, please help! |
Date: | 2006-10-19 13:59:37 |
Message-ID: | 10827.1161266377@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Peter Bauer" <peter(dot)m(dot)bauer(at)gmail(dot)com> writes:
> There is a table called tableregistrations where per day about
> 1 million rows are INSERTed
> 20000 SELECTs should be performed on it
> 10000 UPDATEs should be performed where about 100 rows are updated
> with each execution
> 10000 DELETEs should be performed every 10 seconds
> in such a way that the table constantly contains about 20000 entries.
> A vaccum of the whole database is performed every 10 minutes with
> cron, autovacuum is enabled too.
That's not *nearly* enough given that level of row turnover. You need
to be vacuuming that table about once a minute if not more often, and
you need to be sure that there aren't any long-running transactions that
would prevent vacuum from removing dead rows.
Try a VACUUM VERBOSE after the system has gotten into a slow state to
get more info about exactly what's happening.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | DANTE Alexandra | 2006-10-19 14:05:56 | Re: PostgreSQL and Munin |
Previous Message | Peter Bauer | 2006-10-19 13:52:36 | Re: Overload after some minutes, please help! |