--- AnyEvent/lib/AnyEvent.pm 2008/04/25 07:15:09 1.69 +++ AnyEvent/lib/AnyEvent.pm 2008/04/25 07:29:42 1.71 @@ -866,7 +866,8 @@ =head1 BENCHMARK To give you an idea of the performance and overheads that AnyEvent adds -over the event loops directly, here is a benchmark of various supported +over the event loops themselves (and to give you an impression of the +speed of various event loops), here is a benchmark of various supported event models natively and with anyevent. The benchmark creates a lot of timers (with a zero timeout) and io watchers (watching STDOUT, a pty, to become writable, which it is), lets them fire exactly once and destroys @@ -895,22 +896,22 @@ invoked "watcher" times, it would C<< ->broadcast >> a condvar once to signal the end of this phase. -I is the time, in microseconds, that it takes destroy a single +I is the time, in microseconds, that it takes to destroy a single watcher. =head2 Results name watcher bytes create invoke destroy comment EV/EV 400000 244 0.56 0.46 0.31 EV native interface - EV/Any 100000 610 3.52 0.91 0.75 + EV/Any 100000 610 3.52 0.91 0.75 EV + AnyEvent watchers CoroEV/Any 100000 610 3.49 0.92 0.75 coroutines + Coro::Signal - Perl/Any 10000 654 4.64 1.22 0.77 pure perl implementation - Event/Event 10000 523 28.05 21.38 5.22 Event native interface - Event/Any 10000 943 34.43 20.48 1.39 + Perl/Any 16000 654 4.64 1.22 0.77 pure perl implementation + Event/Event 16000 523 28.05 21.38 0.86 Event native interface + Event/Any 16000 943 34.43 20.48 1.39 Event + AnyEvent watchers Glib/Any 16000 1357 96.99 12.55 55.51 quadratic behaviour Tk/Any 2000 1855 27.01 66.61 14.03 SEGV with >> 2000 watchers - POE/Select 2000 6343 94.69 807.65 562.69 POE::Loop::Select - POE/Event 2000 6644 108.15 768.19 14.33 POE::Loop::Event + POE/Event 2000 6644 108.15 768.19 14.33 via POE::Loop::Event + POE/Select 2000 6343 94.69 807.65 562.69 via POE::Loop::Select =head2 Discussion