perl.loop...Re: benchmarking various event loops with and without anyevent by Rocco Caputo- April 28, 2008 On Apr 28, 2008, at 03:21, Marc Lehmann wrote:>> In all fairness, I want to point out that, after _multiple_ rounds of> longish e-mail exchanges, Rocco Caputo could not solve the problems > that> forced AnyEvent to use this design, nor did he enlighten me on how > to work> around the specific problems that I mentioned to him that forced this> design decision().Addressed in <629C022B-BF10-4461-9D52-8F305D2051DCpobox.com>. Please respond there.> He did not...http://www.nntp.perl.org/group/perl.loop/2008/04/msg1119.html Re: benchmarking various event loops with and without anyevent by Rocco Caputo- April 28, 2008 On Apr 28, 2008, at 06:24, Marc Lehmann wrote:> most important points first>>> In your case, I would create a single persistent POE::Session >> instance>> that serviced all the watchers.>> I would, too, but I cannot find a way to do that with POE: sessions> without active watchers will be destroyed, forcing the session to have> active resources will make the program never-ending.>> I already told you that I tried this approach, and why I couldn&39;t ...http://www.nntp.perl.org/group/perl.loop/2008/04/msg1118.html Re: benchmarking various event loops with and without anyevent by Marc Lehmann- April 28, 2008 most important points first> In your case, I would create a single persistent POE::Session instance > that serviced all the watchers.I would, too, but I cannot find a way to do that with POE: sessionswithout active watchers will be destroyed, forcing the session to haveactive resources will make the program never-ending.I already told you that I tried this approach, and why I couldn&39;t get itworking.You kepe repeating how it could be designed better, but you never actuallysay how to...http://www.nntp.perl.org/group/perl.loop/2008/04/msg1117.html Re: benchmarking various event loops with and without anyevent by Rocco Caputo- April 28, 2008 On Apr 28, 2008, at 03:21, Marc Lehmann wrote:> On Sat, Apr 26, 2008 at 08:13:27AM -0400, Rocco Caputo <rcaputopobox.com > > wrote:>> each event watcher. Anyone who knows POE can tell you this is one of>> the least efficient designs possible. In fact, this design is worse>> than the average for first-time POE users.>> He then called my model fundamentally broken in private mail and the> documentation rude and unprofessional, without bringing up any >.http://www.nntp.perl.org/group/perl.loop/2008/04/msg1116.html Re: benchmarking various event loops with and without anyevent by Rocco Caputo- April 28, 2008 On Apr 27, 2008, at 00:56, Marc Lehmann wrote:> On Sat, Apr 26, 2008 at 08:13:27AM -0400, Rocco Caputo <rcaputopobox.com > > wrote:>> each event watcher. Anyone who knows POE can tell you this is one of>> the least efficient designs possible.>> It is the only design that I could get working, even after > consulting a> few people and implementing some workarounds for the bugs in POE.>> In any case, you have to consider that most people on this...http://www.nntp.perl.org/group/perl.loop/2008/04/msg1115.html Re: benchmarking various event loops with and without anyevent by Marc Lehmann- April 28, 2008 On Sat, Apr 26, 2008 at 08:13:27AM -0400, Rocco Caputo <rcaputopobox.com> wrote:> each event watcher. Anyone who knows POE can tell you this is one of > the least efficient designs possible. In fact, this design is worse > than the average for first-time POE users.He then called my model fundamentally broken in private mail and thedocumentation rude and unprofessional, without bringing up any evidenceIn all fairness, I want to point out that, after _multiple_ rounds oflongish.http://www.nntp.perl.org/group/perl.loop/2008/04/msg1114.html Re: benchmarking various event loops with and without anyevent by Marc Lehmann- April 26, 2008 On Sat, Apr 26, 2008 at 08:13:27AM -0400, Rocco Caputo <rcaputopobox.com> wrote:> each event watcher. Anyone who knows POE can tell you this is one of > the least efficient designs possible.It is the only design that I could get working, even after consulting afew people and implementing some workarounds for the bugs in POE.In any case, you have to consider that most people on this planetdon&39;t know POE, and even if, they don&39;t know it that well. Since thedocumentation for...http://www.nntp.perl.org/group/perl.loop/2008/04/msg1113.html Re: benchmarking various event loops with and without anyevent by Rocco Caputo- April 26, 2008 On Apr 25, 2008, at 22:46, Marc Lehmann wrote:>> The next release of AnyEvent contains support for a few more > "backends",> notably POE, so AnyEvent is now by definition compatible to POE > (before it> was only compatible when using an even loop used by POE, such as > Event or> EV that could be shared).> The results were mostly as expected, with EV leading and POE being> abysmal.It&39;s no wonder that AnyEvent::Impl::POE runs so slowly. According to .http://www.nntp.perl.org/group/perl.loop/2008/04/msg1112.html Re: benchmarking various event loops with and without anyevent by Uri Guttman- April 26, 2008 >>>>> "ML" == Marc Lehmann <schmorpschmorp.de> writes: ML> On Fri, Apr 25, 2008 at 11:40:03PM -0400, Uri Guttman <uristemsystems.com> wrote: >> check out stem&39;s pure perl event loop. there are examples in the ML> Maybe I&39;ll provide a backend for stem.actually it makes more sense to me to wrap anyevent in stem. it alreadyhas several event wrappers (pure perl, event.pm and tk) and wrapping isvery easy to do. not much different than the...http://www.nntp.perl.org/group/perl.loop/2008/04/msg1110.html Re: benchmarking various event loops with and without anyevent by Uri Guttman- April 26, 2008 >>>>> "ML" == Marc Lehmann <schmorpschmorp.de> writes: ML> The surprising one was the pure perl implementation, which was quite on ML> par with C-based event loops such as Event or Glib. I did expect the pure ML> perl implementatioon to be at least a factor of three slower than Event or ML> Glib. ML> As the pure perl loop wasn&39;t written with high performance in mind, this ML> prompted me to optimise it for some important cases (mostly to.http://www.nntp.perl.org/group/perl.loop/2008/04/msg1111.html |