| From: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Dimitri Fontaine <dim(at)tapoueh(dot)org> |
| Subject: | Re: Built-in connection pooler |
| Date: | 2019-07-15 14:04:47 |
| Message-ID: | fb171cef-95ad-af8b-e38d-e52eb84dae6b@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| builtin_connection_proxy-7.patch | text/x-patch | 103.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2019-07-15 14:18:55 | Re: SHOW CREATE |
| Previous Message | Robert Haas | 2019-07-15 13:49:32 | Re: Adding SMGR discriminator to buffer tags |