in reply to Re^7: Help designing a threaded service
in thread Help designing a threaded service
Hm. The description was based upon the implementation of nginx server.The article you linked is factually incorrect (looks to me like a work of some intern from zimbra). Nginx workers don't fight for the accept_mutex after they got events from the listening socket, but they lock this mutex before they subscribe to events from it (see implementation). The reason is to not waste CPU, not to avoid accepting the same connection in different workers, which won't happen even if you disable this option. Anyways, nginx running event loop and OP is seems more interested in traditional prefork options (otherwise he should look at AnyEvent or Mojolicious instead of Net::Server) which simply block in accept, so it is hardly relevant.
PS is it this guy? That's funny
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^9: Help designing a threaded service
by BrowserUk (Patriarch) on Jan 27, 2014 at 21:08 UTC | |
by Anonymous Monk on Jan 28, 2014 at 01:22 UTC | |
by BrowserUk (Patriarch) on Jan 28, 2014 at 05:39 UTC | |
by zwon (Abbot) on Jan 28, 2014 at 15:03 UTC |
In Section
Seekers of Perl Wisdom