Also, I'd like to add that we don't generally want to block, even for select(). In our framework, the application may have numerous tasks to do when it is not servicing IO. This necessitates using select to poll all the sockets, with the associated setup overhead. select() as such is recognized as scaling badly, even on unix() which is why (I've been told) there are now alternatives for asynchronous IO commonly available on linux. K
From: [email protected] [mailto:[email protected]] On Behalf Of Kristján Valur Jónsson Sent: 14. júlí 2009 23:08 To: Larry Dickson Cc: Henning Diedrich; [email protected] Subject: Re: [Stackless] irc threads Well, on Windows, one of the rules of efficient network programming is to not use select(). See: http://tangentsoft.net/wskfaq/articles/io-strategies.html and http://msdn.microsoft.com/en-us/magazine/dvdarchive/cc302334.aspx select() is discouraged on windows except for compatibility reasons, since it works contrary to the internal IO scheduling mechanisms. K From: Larry Dickson [mailto:[email protected]] Sent: 14. júlí 2009 15:34 To: Kristján Valur Jónsson Cc: Henning Diedrich; [email protected] Subject: Re: [Stackless] irc threads There seems to be a false assumption here: select does not "poll the sockets" (or anything else) and it is not inefficient. In fact, it blocks until one of the events in question takes place, then reawakens a single process (e.g. main tasklet). This is as efficient as you can get, and "native facilities" are almost certainly just doing the same thing in a hidden place. Larry Dickson Cutting Edge Networked Storage On 7/9/09, Kristján Valur Jónsson <[email protected]<mailto:[email protected]>> wrote: StacklessIO is written in C++. It uses native facilities to notify an internal event queue when an IO request has completed, instead of requiring the "main tasklet" to regularly poll the sockets using select() which is inefficient. This aims to minimize latency and reduce overhead. It can also use the async. notification facility of the python C api to wake up sleeping tasklets without requiring the main tasklet to poll the event queue. It is also more 'complete' in its emulation of the native socket module, I think. But performance tests by Richard on his module have still shown it to be very capable, and to scale better than threaded solutions like your irc server, so it may well be quite adequate for the task. K > -----Original Message----- > From: Henning Diedrich > [mailto:[email protected]<mailto:[email protected]>] > Sent: 9. júlí 2009 14:02 > To: Kristján Valur Jónsson; > [email protected]<mailto:[email protected]> > Subject: Re: [Stackless] irc threads > > > > Kristján Valur Jónsson wrote: > > Yes, stacklessIO is designed to do that for you, to provide a > transparently tasklet-blocking replacement module for socket and > others. > > However, I hven't still managed to release it (although I do intend > to as soon as I can) and it is at them moment Windows only, and likely > to remain so for a bit. > > > > Meanwhile, there is Richard Tew's async socket implementation. > > > > K > > > > Thanks for the clarification. What is the difference between > stacklessIO > and Richard's implementation? This question is probably naive but maybe > some pointers are possible? > > Thanks, > Henning _______________________________________________ Stackless mailing list [email protected]<mailto:[email protected]> http://www.stackless.com/mailman/listinfo/stackless
_______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
