Hello PostgreSQL developers,
first, happy new year to you all!
I recently got this bug report through Debian. I can confirm that on
an otherwise idle system, and with no connections to PostgreSQL at
all, I get
8,5% ( 11,5) postgres : schedule_hrtimeout_range (hrtimer_wak=
eup)=20
in powertop. Now, 11 wakeups per minute is not dramatic, and with
PostgreSQL being a server application, perfect power management is
certainly the least concern for you.=20
However, it would be interesting to know whether those wakeups are
intended and necessary, or if they would be easy or hard to fix. (I
have no problem with closing the bug as wontfix, but I'd like to give
a rationale).
Thank you!
Martin
----- Forwarded message from Xavier Bestel <xavier.bestel@free.fr> -----
Subject: Bug#506196: postgresql: consume too much power when idle (>10 wake=
ups/second)
Reply-To: Xavier Bestel <xavier.bestel@free.fr>, 506196@bugs.debian.org
From: Xavier Bestel <xavier.bestel@free.fr>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Date: Wed, 19 Nov 2008 10:12:05 +0100
Package: postgresql
Version: 8.3.5-1
Severity: minor
Hi,
postgresql is installed on my machine because it was pulled by another pack=
age
(can't remember which one). It doesn't do anything special, but it still do=
es more
then 10 wakeups/second on that system, uselessly. If idle, it shouldn't eve=
n appear
in powertop's profile.
Thanks,
Xav
----- End forwarded message -----
--=20
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)