[pgpool-general: 3934] accept() scalability issues

Michael Renner michael.renner at amd.co.at
Fri Aug 7 01:52:18 JST 2015


we operate a pgpool-II setup (running 3.3.6) configured with ~1200 children and noticed heavy context switching & CPU time spent in the kernel.

While looking through the source I noticed that pgpool neither uses an event-based approach like epoll or kqueue, nor does it use serializing mechanisms like semaphores to reduce contention around the select/accept loop.

http://uwsgi-docs.readthedocs.org/en/latest/articles/SerializingAccept.html <http://uwsgi-docs.readthedocs.org/en/latest/articles/SerializingAccept.html> describes the generic problem.

Do you have any plans to implement an event- or lock-based approach in pgpool?

all the best,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20150806/a56928ed/attachment.html>

More information about the pgpool-general mailing list