From: Francis Cianfrocca Date: 2007-01-18T11:54:08+09:00 Subject: Re: Eventmachine - pure Ruby port ------=_Part_100547_17328706.1169088845770 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 1/17/07, Mark Haliday wrote: > > Jason Roelofs wrote: > > > > Just a warning, the pure-Ruby EM is dog slow comparatively. I'd suggest > > using the native version if you can. > > This is something I'm wondering about. I've seen and used Twisted for > Python and its robust and can handle large amounts of traffic. I wonder > why Ruby seems to lack the robustness in the arena of sockets, etc. that > Python seems to have no issues with? Perhaps I'm seeing this all wrong, > so please correct me. Eventmachine as it is now is coded in C or C++, > correct? Yet even with the improvements in the Ruby core for sockets > the pure implementation of EM is going to be much slower. I have to > think Ruby has some issues still then in the arena of sockets? Will > YARV help any? I've done some experiments with the low-level pure Ruby socket functions and with all the cruft stripped out, pure Ruby is about half as fast as C in tests that heavily stress network I/O. That's life in the big city, I think, but the hybrid EM will always be supported. I envision that as the alternative for really high-stress and high-scale applications, and I believe EM will be able to handle most of the requirements people can throw at it. By the way, is anyone interested in joining the team? Tony is now an EM committer and I'd like to have some more. Especially people who know a lot about Twisted. I want to see EM match Twisted's feature set. As far as stability is concerned, EM is in a very good place now, but it needs a lot more features, a lot more documentation, case studies, and evangelism. ------=_Part_100547_17328706.1169088845770--