[ViewVC] Diff of: cvs/AnyEvent/lib/AnyEvent.pm

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.94 by root, Sat Apr 26 04:33:51 2008 UTC vs.
Revision 1.100 by elmex, Sun Apr 27 19:15:43 2008 UTC

 Of course, if you want lots of policy (this can arguably be somewhat
 useful) and you want to force your users to use the one and only event
 model, you should I<not> 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
 L<AnyEvent> provides an identical interface to multiple event loops. This
 allows module authors to utilise an event loop without forcing module
 might chose the wrong one unless you load the correct one yourself.
 You can chose to use a rather inefficient pure-perl implementation by
 loading the C<AnyEvent::Impl::Perl> module, which gives you similar
 behaviour everywhere, but letting AnyEvent chose is generally better.
+=head1 OTHER MODULES
+L<AnyEvent> itself comes with useful utility modules:
+To make it easier to do non-blocking IO the modules L<AnyEvent::Handle>
+and L<AnyEvent::Socket> are provided. L<AnyEvent::Handle> provides
+read and write buffers and manages watchers for reads and writes.
+L<AnyEvent::Socket> 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<AnyEvent::FastPing>
+=item L<Net::IRC3>
+=item L<Net::XMPP2>
+=back
 =cut
 package AnyEvent;
          EV/EV   400000   244   0.56   0.46    0.31 EV native interface
         EV/Any   100000   244   2.50   0.46    0.29 EV + AnyEvent watchers
     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
     POE/Select     2000  6343  94.13 809.12  565.96 via POE::Loop::Select
 well. For example, a select-based event loop (such as the pure perl one)
 can never compete with an event loop that uses epoll when the number of
 file descriptors grows high. In this benchmark, all events become ready at
 the same time, so select/poll-based implementations get an unnatural speed
 boost.
+Also, note that the number of watchers usually has a nonlinear effect on
+overall speed, that is, creating twice as many watchers doesn't take twice
+the time - usually it takes longer. This puts event loops tested with a
+higher number of watchers at a disadvantage.
+To put the range of results into perspective, consider that on the
+benchmark machine, handling an event takes roughly 1600 CPU cycles with
+EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU
+cycles with POE.
 C<EV> is the sole leader regarding speed and memory use, which are both
 maximal/minimal, respectively. Even when going through AnyEvent, it uses
 far less memory than any other event loop and is still faster than Event
 natively.
 =head3 Results
     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
 =head3 Discussion
 =head3 Results
     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
 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.
 The C-based event loops Event and Glib come in second this time, as the
 overhead of running an iteration is much smaller in C than in Perl (little
 code to execute in the inner loop, and perl's function calling overhead is
 high, and updating all the data structures is costly).
 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
 =over 4

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing AnyEvent/lib/AnyEvent.pm (file contents): Revision 1.94 by root, Sat Apr 26 04:33:51 2008 UTC vs. Revision 1.100 by elmex, Sun Apr 27 19:15:43 2008 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.94 by root, Sat Apr 26 04:33:51 2008 UTC vs.
Revision 1.100 by elmex, Sun Apr 27 19:15:43 2008 UTC