--- AnyEvent/lib/AnyEvent.pm 2008/04/26 11:16:16 1.96 +++ AnyEvent/lib/AnyEvent.pm 2008/04/27 19:15:43 1.100 @@ -68,6 +68,25 @@ useful) and you want to force your users to use the one and only event model, you should I use this module. +#TODO# + +Net::IRC3 +AnyEvent::HTTPD +AnyEvent::DNS +IO::AnyEvent +Net::FPing +Net::XMPP2 +Coro + +AnyEvent::IRC +AnyEvent::HTTPD +AnyEvent::DNS +AnyEvent::Handle +AnyEvent::Socket +AnyEvent::FPing +AnyEvent::XMPP +AnyEvent::SNMP +Coro =head1 DESCRIPTION @@ -460,6 +479,28 @@ loading the C module, which gives you similar behaviour everywhere, but letting AnyEvent chose is generally better. +=head1 OTHER MODULES + +L itself comes with useful utility modules: + +To make it easier to do non-blocking IO the modules L +and L are provided. L provides +read and write buffers and manages watchers for reads and writes. +L provides means to do non-blocking connects. + +Aside from those there are these modules that support AnyEvent (and use it +for non-blocking IO): + +=over 4 + +=item L + +=item L + +=item L + +=back + =cut package AnyEvent; @@ -946,7 +987,7 @@ CoroEV/Any 100000 244 2.49 0.44 0.29 coroutines + Coro::Signal Perl/Any 100000 513 4.92 0.87 1.12 pure perl implementation Event/Event 16000 516 31.88 31.30 0.85 Event native interface - Event/Any 16000 936 39.17 33.63 1.43 Event + AnyEvent watchers + Event/Any 16000 590 35.75 31.42 1.08 Event + AnyEvent watchers Glib/Any 16000 1357 98.22 12.41 54.00 quadratic behaviour Tk/Any 2000 1860 26.97 67.98 14.00 SEGV with >> 2000 watchers POE/Event 2000 6644 108.64 736.02 14.73 via POE::Loop::Event @@ -1069,7 +1110,7 @@ name sockets create request EV 20000 69.01 11.16 - Perl 20000 75.28 112.76 + Perl 20000 73.32 35.87 Event 20000 212.62 257.32 Glib 20000 651.16 1896.30 POE 20000 349.67 12317.24 uses POE::Loop::Event @@ -1125,9 +1166,9 @@ name sockets create request EV 16 20.00 6.54 + Perl 16 25.75 12.62 Event 16 81.27 35.86 Glib 16 32.63 15.48 - Perl 16 24.62 162.37 POE 16 261.87 276.28 uses POE::Loop::Event =head3 Discussion @@ -1135,7 +1176,9 @@ The benchmark tries to test the performance of a typical small server. While knowing how various event loops perform is interesting, keep in mind that their overhead in this case is usually not as important, due -to the small absolute number of watchers. +to the small absolute number of watchers (that is, you need efficiency and +speed most when you have lots of watchers, not when you only have a few of +them). EV is again fastest. @@ -1146,7 +1189,7 @@ The pure perl event loop is much slower, but still competitive. -POE also performs much better in this case, but is is stillf ar behind the +POE also performs much better in this case, but is is still far behind the others. =head3 Summary