Boost C++ Libraries: Ticket #4732: Event Ports for Solaris https://svn.boost.org/trac10/ticket/4732 <p> Hi, </p> <p> Is it possible to add support for event ports on the Solaris platform? I've written an application that uses the thread-pool strategy from the HTTP Server 2 example. As I understand, the /dev/poll method on Solaris needs lots of synchronization between threads. </p> <p> I've noticed that my application does not nearly scale linearly with an increase in threads. Highest throughput is obtained at approximately 7 threads, after which I get diminishing returns. I think this could be due to the inter-thread synchronization needed to access /dev/poll? Please find 2 links detailing event ports and/or comparison with /dev/poll. </p> <p> Jacques </p> <h2 class="section" id="http:blogs.sun.comdapentryevent_ports_and_performance"><a class="ext-link" href="http://blogs.sun.com/dap/entry/event_ports_and_performance"><span class="icon">​</span>http://blogs.sun.com/dap/entry/event_ports_and_performance</a></h2> <h2 class="section" id="http:developers.sun.comsolarisarticlesevent_completion.html"><a class="ext-link" href="http://developers.sun.com/solaris/articles/event_completion.html"><span class="icon">​</span>http://developers.sun.com/solaris/articles/event_completion.html</a></h2> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/4732 Trac 1.4.3 chris_kohlhoff Sat, 16 Oct 2010 08:19:57 GMT <link>https://svn.boost.org/trac10/ticket/4732#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/4732#comment:1</guid> <description> <p> If you are using the HTTP Server 2 design (io_service-per-CPU) then there is no contended synchronization in asio with respect to /dev/poll. Each io_service would have its own /dev/poll descriptor. The sub-linear scaling might be due to something else. </p> <p> Realistically, support for event ports would need to be sponsored/funded. Please let me know if you are interested in pursuing that option. </p> </description> <category>Ticket</category> </item> </channel> </rss>