Re: Built-in connection pooler - Mailing list pgsql-hackers

From Konstantin Knizhnik
Subject Re: Built-in connection pooler
Date
Msg-id fb171cef-95ad-af8b-e38d-e52eb84dae6b@postgrespro.ru
Whole thread Raw
In response to Re: Built-in connection pooler  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Built-in connection pooler  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Re: Built-in connection pooler  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers

On 14.07.2019 8:03, Thomas Munro wrote:
>
> On my FreeBSD box (which doesn't have epoll(), so it's latch.c's old
> school poll() for now), I see the connection proxy process eating a
> lot of CPU and the temperature rising.  I see with truss that it's
> doing this as fast as it can:
>
> poll({ 13/POLLIN 17/POLLIN|POLLOUT },2,1000)     = 1 (0x1)
>
> Ouch.  I admit that I had the idea to test on FreeBSD because I
> noticed the patch introduces EPOLLET and I figured this might have
> been tested only on Linux.  FWIW the same happens on a Mac.
>
I have committed patch which emulates epoll EPOLLET flag and so should 
avoid busy loop with poll().
I will be pleased if you can check it at FreeBSD  box.



Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Adding SMGR discriminator to buffer tags
Next
From: Robert Haas
Date:
Subject: Re: SHOW CREATE