<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class=""><a href="http://uwsgi-docs.readthedocs.org/en/latest/articles/SerializingAccept.html" class="">http://uwsgi-docs.readthedocs.org/en/latest/articles/SerializingAccept.html</a> describes the generic problem.</div><div class=""><br class=""></div><div class="">Do you have any plans to implement an event- or lock-based approach in pgpool?</div><div class=""><br class=""></div><div class="">all the best,</div><div class="">Michael</div></body></html>