> On Apr 10, 2018, at 9:05 PM, Thomas Munro <thomas.mu...@enterprisedb.com> > wrote: > > On Wed, Dec 6, 2017 at 12:53 AM, Thomas Munro > <thomas.mu...@enterprisedb.com> wrote: >> On Thu, Jun 22, 2017 at 7:19 PM, Thomas Munro >> <thomas.mu...@enterprisedb.com> wrote: >>> I don't plan to resubmit this patch myself, but I was doing some >>> spring cleaning and rebasing today and I figured it might be worth >>> quietly leaving a working patch here just in case anyone from the >>> various BSD communities is interested in taking the idea further. > > I heard through the grapevine of some people currently investigating > performance problems on busy FreeBSD systems, possibly related to the > postmaster pipe. I suspect this patch might be a part of the solution > (other patches probably needed to get maximum value out of this patch: > reuse WaitEventSet objects in some key places, and get rid of high > frequency PostmasterIsAlive() read() calls). The autoconf-fu in the > last version bit-rotted so it seemed like a good time to post a > rebased patch. > > -- > Thomas Munro > http://www.enterprisedb.com > <kqueue-v9.patch>
Hi, I’m instrested in the kqueue patch and would like to know its current state and possible timeline for inclusion in the base code. I have several large FreeBSD systems running PostgreSQL 11 that I believe currently displays this issue. The system has 88 vCPUs, 512GB Ram, and very active application with over 1000 connections to the database. The system exhibits high kernel CPU usage servicing poll() for connections that are idle. I’ve being testing pg_bouncer to reduce the number of connections and thus system CPU usage; however, not all connections can go through pg_bouncer. Thanks, Rui.
