too low NAPTIME_PER_CYCLE /too many wakeups in walreceiver.c

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: too low NAPTIME_PER_CYCLE /too many wakeups in walreceiver.c
Date: 2012-05-30 12:57:07
Message-ID: 201205301457.07444.andres@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Currently the walreceiver wakeups NAPTIME_PER_CYCLE=100 miliseconds in idle
state. This is rather frequent. I don't really see any reason to do so.
A nice fix would be to latchify that with WaitLatchOrSocket + a SetLatch in
the signal handler for shutdown but that seems to be too invasive at that
point. So I suggest simply increasing NAPTIME_PER_CYCLE to 500 or 1000ms?

Andres

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2012-05-30 13:33:48 Re: hash index concurrency
Previous Message Peter Geoghegan 2012-05-30 12:54:07 Re: Uh, I change my mind about commit_delay + commit_siblings (sort of)