From: | "Peter Bauer" <peter(dot)m(dot)bauer(at)gmail(dot)com> |
---|---|
To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Major Performance decrease after some hours |
Date: | 2006-10-01 18:27:27 |
Message-ID: | 764c9e910610011127u1bbb777ep21039e118726a90a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2006/10/1, Matthew T. O'Connor <matthew(at)zeut(dot)net>:
> MaXX wrote:
> >> There are 10-15 postmaster processes running which use all the CPU
> >> power.
> >> A restart of tomcat and then postgresql results in the same situation.
> >> Some postgres processes are in DELETE waiting or SELECT waiting.
> >> VACUUM runs through in just about 1-2 seconds and is run via cron
> >> every minute and reports that the fsm setting are high enough.
> >
> > Pure speculation: are you sure you aren't vacuuming too agressively?
>
> Have you tried autovacuum? You can manually tweak the settings so that
> your hot spot tables are vacuumed aggressivly. One of the main upsides
> to autovacuum is tha tit saves cycles, that is, it only vacuums when you
> need it.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
Autovacuum is enabled and runs in addition to the configured cronjob
vacuums. I will attach logfiles to the reply to Toms mail, so please
have a look at it if autovacuum can be reconfigured to replace the
cronjobs.
thx,
Peter
From | Date | Subject | |
---|---|---|---|
Next Message | Yannick Warnier | 2006-10-01 18:43:47 | GiST and Gin technical doc |
Previous Message | Peter Bauer | 2006-10-01 18:25:58 | Re: Major Performance decrease after some hours |