| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | "Harvey, Allan AC" <HarveyA(at)OneSteel(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Performance suggestions? |
| Date: | 2004-12-15 00:36:50 |
| Message-ID: | 1103071010.28882.60.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2004-12-15 at 10:22 +1100, Harvey, Allan AC wrote:
> I have a small table about 20 rows, a constant, that is receiving
> about 160 updates per second.
> The table is used to share gathered data to other process asynchronously.
> After 5 min it is 12 updates per second.
> Performance returns after a vacuum analyse.
It should be quite feasible to VACUUM this table frequently (once per
minute or even more often).
> Or should I just stick to saving the data, inserts seem to go on and on, and
> use a different IPC method.
MVCC isn't really ideal for this kind of situation, but without knowing
more about your application it's difficult to say whether switching to
another IPC method would be a better choice.
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2004-12-15 00:39:28 | Re: Corrupt RTREE index |
| Previous Message | Neil Conway | 2004-12-15 00:33:49 | Re: Performance differences 7.1 to 7.3 |