Re: Debian Bug#506196: postgresql: consume too much power when idle (>10 wakeups/second)

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: pgsql-bugs(at)postgresql(dot)org, 506196(at)bugs(dot)debian(dot)org
Subject: Re: Debian Bug#506196: postgresql: consume too much power when idle (>10 wakeups/second)
Date: 2009-01-04 21:22:19
Message-ID: 20090104212219.GC26552@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Martin Pitt wrote:
> Hi Alvaro,
>
> Alvaro Herrera [2009-01-04 18:05 -0300]:
> > How many databases are there?
>
> It's a freshly created instance, thus just "template[01]" and
> "postgres". Standard 8.3 autovacuum is enabled.

I think we must blame bgwriter then. I had a look at it some time ago
to how hard would it be to remove the useless wakeups and concluded that
it wasn't really worth the trouble. Not that I looked that hard;
probably someone smarter (and/or with more time) can find ways to
optimize it. See BgWriterNap in

http://git.postgresql.org/?p=postgresql.git;a=blob;f=src/backend/postmaster/bgwriter.c

(Note that with the current code, you can put it to rest for 10 seconds
at a time by setting bgwriter_lru_maxpages to 0 in postgresql.conf)

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2009-01-04 23:00:29 Re: Debian Bug#506196: postgresql: consume too much power when idle (>10 wakeups/second)
Previous Message Martin Pitt 2009-01-04 21:15:36 Re: Debian Bug#506196: postgresql: consume too much power when idle (>10 wakeups/second)