--- AnyEvent/lib/AnyEvent.pm	2008/04/27 19:36:55	1.101
+++ AnyEvent/lib/AnyEvent.pm	2008/04/30 11:40:22	1.104
@@ -392,8 +392,8 @@
    AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.
    AnyEvent::Impl::EV        based on EV (an interface to libev, best choice).
    AnyEvent::Impl::Event     based on Event, second best choice.
+   AnyEvent::Impl::Perl      pure-perl implementation, fast and portable.
    AnyEvent::Impl::Glib      based on Glib, third-best choice.
-   AnyEvent::Impl::Perl      pure-perl implementation, inefficient but portable.
    AnyEvent::Impl::Tk        based on Tk, very bad choice.
    AnyEvent::Impl::Qt        based on Qt, cannot be autoprobed (see its docs).
    AnyEvent::Impl::EventLib  based on Event::Lib, leaks memory and worse.
@@ -555,12 +555,12 @@
    [Coro::Event::          => AnyEvent::Impl::CoroEvent::],
    [EV::                   => AnyEvent::Impl::EV::],
    [Event::                => AnyEvent::Impl::Event::],
-   [Glib::                 => AnyEvent::Impl::Glib::],
    [Tk::                   => AnyEvent::Impl::Tk::],
    [Wx::                   => AnyEvent::Impl::POE::],
    [Prima::                => AnyEvent::Impl::POE::],
    [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],
    # everything below here will not be autoprobed as the pureperl backend should work everywhere
+   [Glib::                 => AnyEvent::Impl::Glib::],
    [Event::Lib::           => AnyEvent::Impl::EventLib::], # too buggy
    [Qt::                   => AnyEvent::Impl::Qt::],       # requires special main program
    [POE::Kernel::          => AnyEvent::Impl::POE::],      # lasciate ogni speranza
@@ -1073,17 +1073,22 @@
 hidden memory cost inside the kernel which is not reflected in the figures
 above).
 
-C<POE>, regardless of underlying event loop (whether using its pure
-perl select-based backend or the Event module, the POE-EV backend
-couldn't be tested because it wasn't working) shows abysmal performance
-and memory usage: Watchers use almost 30 times as much memory as
-EV watchers, and 10 times as much memory as Event (the high memory
+C<POE>, regardless of underlying event loop (whether using its pure perl
+select-based backend or the Event module, the POE-EV backend couldn't
+be tested because it wasn't working) shows abysmal performance and
+memory usage with AnyEvent: Watchers use almost 30 times as much memory
+as EV watchers, and 10 times as much memory as Event (the high memory
 requirements are caused by requiring a session for each watcher). Watcher
 invocation speed is almost 900 times slower than with AnyEvent's pure perl
-implementation. The design of the POE adaptor class in AnyEvent can not
-really account for this, as session creation overhead is small compared
-to execution of the state machine, which is coded pretty optimally within
-L<AnyEvent::Impl::POE>. POE simply seems to be abysmally slow.
+implementation.
+
+The design of the POE adaptor class in AnyEvent can not really account
+for the performance issues, though, as session creation overhead is
+small compared to execution of the state machine, which is coded pretty
+optimally within L<AnyEvent::Impl::POE> (and while everybody agrees that
+using multiple sessions is not a good approach, especially regarding
+memory usage, even the author of POE could not come up with a faster
+design).
 
 =head3 Summary
 
@@ -1172,8 +1177,7 @@
 
 =over 4
 
-=item * The pure perl implementation performs extremely well, considering
-that it uses select.
+=item * The pure perl implementation performs extremely well.
 
 =item * Avoid Glib or POE in large projects where performance matters.
 
@@ -1212,12 +1216,9 @@
 
 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.
+Perl again comes second. It is noticably faster than the C-based event
+loops Event and Glib, although the difference is too small to really
+matter.
 
 POE also performs much better in this case, but is is still far behind the
 others.
@@ -1235,7 +1236,8 @@
 =head1 FORK
 
 Most event libraries are not fork-safe. The ones who are usually are
-because they are so inefficient. Only L<EV> is fully fork-aware.
+because they rely on inefficient but fork-safe C<select> or C<poll>
+calls. Only L<EV> is fully fork-aware.
 
 If you have to fork, you must either do so I<before> creating your first
 watcher OR you must not use AnyEvent at all in the child.