[ViewVC] Diff of: cvs/AnyEvent/README

Comparing AnyEvent/README (file contents):
Revision 1.50 by root, Sat Aug 1 09:14:54 2009 UTC vs.
Revision 1.52 by root, Mon Aug 10 01:17:38 2009 UTC

         into one. For example, a function that pings many hosts in parallel
         might want to use a condition variable for the whole process.
         Every call to "->begin" will increment a counter, and every call to
         "->end" will decrement it. If the counter reaches 0 in "->end", the
-        (last) callback passed to "begin" will be executed. That callback is
+        (last) callback passed to "begin" will be executed, passing the
-        *supposed* to call "->send", but that is not required. If no
+        condvar as first argument. That callback is *supposed* to call
+        "->send", but that is not required. If no group callback was set,
-        callback was set, "send" will be called without any arguments.
+        "send" will be called without any arguments.
         You can think of "$cv->send" giving you an OR condition (one call
         sends), while "$cv->begin" and "$cv->end" giving you an AND
         condition (all "begin" calls must be "end"'ed before the condvar
         sends).
         that are begung can potentially be zero:
            my $cv = AnyEvent->condvar;
            my %result;
-           $cv->begin (sub { $cv->send (\%result) });
+           $cv->begin (sub { shift->send (\%result) });
            for my $host (@list_of_hosts) {
               $cv->begin;
               ping_host_then_call_callback $host, sub {
                  $result{$host} = ...;
 SUPPORTED EVENT LOOPS/BACKENDS
     The available backend classes are (every class has its own manpage):
     Backends that are autoprobed when no other event loop can be found.
         EV is the preferred backend when no other event loop seems to be in
-        use. If EV is not installed, then AnyEvent will try Event, and,
+        use. If EV is not installed, then AnyEvent will fall back to its own
-        failing that, will fall back to its own pure-perl implementation,
+        pure-perl implementation, which is available everywhere as it comes
-        which is available everywhere as it comes with AnyEvent itself.
+        with AnyEvent itself.
            AnyEvent::Impl::EV        based on EV (interface to libev, best choice).
-           AnyEvent::Impl::Event     based on Event, very stable, few glitches.
            AnyEvent::Impl::Perl      pure-perl implementation, fast and portable.
     Backends that are transparently being picked up when they are used.
         These will be used when they are currently loaded when the first
         watcher is created, in which case it is assumed that the application
         is using them. This means that AnyEvent will automatically pick the
         right backend when the main program loads an event module before
         anything starts to create watchers. Nothing special needs to be done
         by the main program.
+           AnyEvent::Impl::Event     based on Event, very stable, few glitches.
            AnyEvent::Impl::Glib      based on Glib, slow but very stable.
            AnyEvent::Impl::Tk        based on Tk, very broken.
            AnyEvent::Impl::EventLib  based on Event::Lib, leaks memory and worse.
            AnyEvent::Impl::POE       based on POE, very slow, some limitations.
            AnyEvent::Impl::Irssi     used when running within irssi.
     Event::ExecFlow
         High level API for event-based execution flow control.
     Coro
         Has special support for AnyEvent via Coro::AnyEvent.
+SIMPLIFIED AE API
+    Starting with version 5.0, AnyEvent officially supports a second, much
+    simpler, API that is designed to reduce the calling, typing and memory
+    overhead.
+    See the AE manpage for details.
 ERROR AND EXCEPTION HANDLING
     In general, AnyEvent does not do any error handling - it relies on the
     caller to do that if required. The AnyEvent::Strict module (see also the
     "PERL_ANYEVENT_STRICT" environment variable, below) provides strict
     through AnyEvent. The benchmark creates a lot of timers (with a zero
     timeout) and I/O watchers (watching STDOUT, a pty, to become writable,
     which it is), lets them fire exactly once and destroys them again.
     Source code for this benchmark is found as eg/bench in the AnyEvent
-    distribution.
+    distribution. It uses the AE interface, which makes a real difference
+    for the EV and Perl backends only.
    Explanation of the columns
     *watcher* is the number of event watchers created/destroyed. Since
     different event models feature vastly different performances, each event
     loop was given a number of watchers so that overall runtime is
     *destroy* is the time, in microseconds, that it takes to destroy a
     single watcher.
    Results
               name watchers bytes create invoke destroy comment
-             EV/EV   400000   224   0.47   0.35    0.27 EV native interface
+             EV/EV   100000   223   0.47   0.43    0.27 EV native interface
-            EV/Any   100000   224   2.88   0.34    0.27 EV + AnyEvent watchers
+            EV/Any   100000   223   0.48   0.42    0.26 EV + AnyEvent watchers
-        CoroEV/Any   100000   224   2.85   0.35    0.28 coroutines + Coro::Signal
+      Coro::EV/Any   100000   223   0.47   0.42    0.26 coroutines + Coro::Signal
-          Perl/Any   100000   452   4.13   0.73    0.95 pure perl implementation
+          Perl/Any   100000   431   2.70   0.74    0.92 pure perl implementation
-       Event/Event    16000   517  32.20  31.80    0.81 Event native interface
+       Event/Event    16000   516  31.16  31.84    0.82 Event native interface
-         Event/Any    16000   590  35.85  31.55    1.06 Event + AnyEvent watchers
+         Event/Any    16000  1203  42.61  34.79    1.80 Event + AnyEvent watchers
-       IOAsync/Any    16000   989  38.10  32.77   11.13 via IO::Async::Loop::IO_Poll
+       IOAsync/Any    16000  1911  41.92  27.45   16.81 via IO::Async::Loop::IO_Poll
-       IOAsync/Any    16000   990  37.59  29.50   10.61 via IO::Async::Loop::Epoll
+       IOAsync/Any    16000  1726  40.69  26.37   15.25 via IO::Async::Loop::Epoll
-          Glib/Any    16000  1357 102.33  12.31   51.00 quadratic behaviour
+          Glib/Any    16000  1118  89.00  12.57   51.17 quadratic behaviour
-            Tk/Any     2000  1860  27.20  66.31   14.00 SEGV with >> 2000 watchers
+            Tk/Any     2000  1346  20.96  10.75    8.00 SEGV with >> 2000 watchers
-         POE/Event     2000  6328 109.99 751.67   14.02 via POE::Loop::Event
+           POE/Any     2000  6951 108.97 795.32   14.24 via POE::Loop::Event
-        POE/Select     2000  6027  94.54 809.13  579.80 via POE::Loop::Select
+           POE/Any     2000  6648  94.79 774.40  575.51 via POE::Loop::Select
    Discussion
     The benchmark does *not* measure scalability of the event loop very
     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
     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.
     "EV" is the sole leader regarding speed and memory use, which are both
-    maximal/minimal, respectively. Even when going through AnyEvent, it uses
+    maximal/minimal, respectively. When using the AE API there is zero
+    overhead (when going through the AnyEvent API create is about 5-6 times
+    slower, with other times being equal, so still uses far less memory than
-    far less memory than any other event loop and is still faster than Event
+    any other event loop and is still faster than Event natively).
-    natively.
     The pure perl implementation is hit in a few sweet spots (both the
     constant timeout and the use of a single fd hit optimisations in the
     perl interpreter and the backend itself). Nevertheless this shows that
     it adds very little overhead in itself. Like any select-based backend
     In this benchmark, we use 10000 socket pairs (20000 sockets), of which
     100 (1%) are active. This mirrors the activity of large servers with
     many connections, most of which are idle at any one point in time.
     Source code for this benchmark is found as eg/bench2 in the AnyEvent
-    distribution.
+    distribution. It uses the AE interface, which makes a real difference
+    for the EV and Perl backends only.
    Explanation of the columns
     *sockets* is the number of sockets, and twice the number of "servers"
     (as each server has a read and write socket end).
     forwarding it to another server. This includes deleting the old timeout
     and creating a new one that moves the timeout into the future.
    Results
          name sockets create  request
-           EV   20000  69.01    11.16
+           EV   20000  62.66     7.99
-         Perl   20000  73.32    35.87
+         Perl   20000  68.32    32.64
-      IOAsync   20000 157.00    98.14 epoll
+      IOAsync   20000 174.06   101.15 epoll
-      IOAsync   20000 159.31   616.06 poll
+      IOAsync   20000 174.67   610.84 poll
-        Event   20000 212.62   257.32
+        Event   20000 202.69   242.91
-         Glib   20000 651.16  1896.30
+         Glib   20000 557.01  1689.52
-          POE   20000 349.67 12317.24 uses POE::Loop::Event
+          POE   20000 341.54 12086.32 uses POE::Loop::Event
    Discussion
     This benchmark *does* measure scalability and overall performance of the
     particular event loop.

Diff Legend

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

Comparing AnyEvent/README (file contents): Revision 1.50 by root, Sat Aug 1 09:14:54 2009 UTC vs. Revision 1.52 by root, Mon Aug 10 01:17:38 2009 UTC

Diff Legend

Comparing AnyEvent/README (file contents):
Revision 1.50 by root, Sat Aug 1 09:14:54 2009 UTC vs.
Revision 1.52 by root, Mon Aug 10 01:17:38 2009 UTC