ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/AnyEvent/lib/AnyEvent.pm
(Generate patch)

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

… …
65technically possible. 65technically possible.
66 66
67Of course, if you want lots of policy (this can arguably be somewhat 67Of course, if you want lots of policy (this can arguably be somewhat
68useful) and you want to force your users to use the one and only event 68useful) and you want to force your users to use the one and only event
69model, you should I<not> use this module. 69model, you should I<not> use this module.
70
71 70
72=head1 DESCRIPTION 71=head1 DESCRIPTION
73 72
74L<AnyEvent> provides an identical interface to multiple event loops. This 73L<AnyEvent> provides an identical interface to multiple event loops. This
75allows module authors to utilise an event loop without forcing module 74allows module authors to utilise an event loop without forcing module
… …
457might chose the wrong one unless you load the correct one yourself. 456might chose the wrong one unless you load the correct one yourself.
458 457
459You can chose to use a rather inefficient pure-perl implementation by 458You can chose to use a rather inefficient pure-perl implementation by
460loading the C<AnyEvent::Impl::Perl> module, which gives you similar 459loading the C<AnyEvent::Impl::Perl> module, which gives you similar
461behaviour everywhere, but letting AnyEvent chose is generally better. 460behaviour everywhere, but letting AnyEvent chose is generally better.
461
462=head1 OTHER MODULES
463
464The following is a non-exhaustive list of additional modules that use
465AnyEvent and can therefore be mixed easily with other AnyEvent modules
466in the same program. Some of the modules come with AnyEvent, some are
467available via CPAN.
468
469=over 4
470
471=item L<AnyEvent::Util>
472
473Contains various utility functions that replace often-used but blocking
474functions such as C<inet_aton> by event-/callback-based versions.
475
476=item L<AnyEvent::Handle>
477
478Provide read and write buffers and manages watchers for reads and writes.
479
480=item L<AnyEvent::Socket>
481
482Provides a means to do non-blocking connects, accepts etc.
483
484=item L<AnyEvent::HTTPD>
485
486Provides a simple web application server framework.
487
488=item L<AnyEvent::DNS>
489
490Provides asynchronous DNS resolver capabilities, beyond what
491L<AnyEvent::Util> offers.
492
493=item L<AnyEvent::FastPing>
494
495The fastest ping in the west.
496
497=item L<Net::IRC3>
498
499AnyEvent based IRC client module family.
500
501=item L<Net::XMPP2>
502
503AnyEvent based XMPP (Jabber protocol) module family.
504
505=item L<Net::FCP>
506
507AnyEvent-based implementation of the Freenet Client Protocol, birthplace
508of AnyEvent.
509
510=item L<Event::ExecFlow>
511
512High level API for event-based execution flow control.
513
514=item L<Coro>
515
516Has special support for AnyEvent.
517
518=item L<IO::Lambda>
519
520The lambda approach to I/O - don't ask, look there. Can use AnyEvent.
521
522=item L<IO::AIO>
523
524Truly asynchronous I/O, should be in the toolbox of every event
525programmer. Can be trivially made to use AnyEvent.
526
527=item L<BDB>
528
529Truly asynchronous Berkeley DB access. Can be trivially made to use
530AnyEvent.
531
532=back
462 533
463=cut 534=cut
464 535
465package AnyEvent; 536package AnyEvent;
466 537
… …
944 EV/EV 400000 244 0.56 0.46 0.31 EV native interface 1015 EV/EV 400000 244 0.56 0.46 0.31 EV native interface
945 EV/Any 100000 244 2.50 0.46 0.29 EV + AnyEvent watchers 1016 EV/Any 100000 244 2.50 0.46 0.29 EV + AnyEvent watchers
946 CoroEV/Any 100000 244 2.49 0.44 0.29 coroutines + Coro::Signal 1017 CoroEV/Any 100000 244 2.49 0.44 0.29 coroutines + Coro::Signal
947 Perl/Any 100000 513 4.92 0.87 1.12 pure perl implementation 1018 Perl/Any 100000 513 4.92 0.87 1.12 pure perl implementation
948 Event/Event 16000 516 31.88 31.30 0.85 Event native interface 1019 Event/Event 16000 516 31.88 31.30 0.85 Event native interface
949 Event/Any 16000 936 39.17 33.63 1.43 Event + AnyEvent watchers 1020 Event/Any 16000 590 35.75 31.42 1.08 Event + AnyEvent watchers
950 Glib/Any 16000 1357 98.22 12.41 54.00 quadratic behaviour 1021 Glib/Any 16000 1357 98.22 12.41 54.00 quadratic behaviour
951 Tk/Any 2000 1860 26.97 67.98 14.00 SEGV with >> 2000 watchers 1022 Tk/Any 2000 1860 26.97 67.98 14.00 SEGV with >> 2000 watchers
952 POE/Event 2000 6644 108.64 736.02 14.73 via POE::Loop::Event 1023 POE/Event 2000 6644 108.64 736.02 14.73 via POE::Loop::Event
953 POE/Select 2000 6343 94.13 809.12 565.96 via POE::Loop::Select 1024 POE/Select 2000 6343 94.13 809.12 565.96 via POE::Loop::Select
954 1025
… …
958well. For example, a select-based event loop (such as the pure perl one) 1029well. For example, a select-based event loop (such as the pure perl one)
959can never compete with an event loop that uses epoll when the number of 1030can never compete with an event loop that uses epoll when the number of
960file descriptors grows high. In this benchmark, all events become ready at 1031file descriptors grows high. In this benchmark, all events become ready at
961the same time, so select/poll-based implementations get an unnatural speed 1032the same time, so select/poll-based implementations get an unnatural speed
962boost. 1033boost.
1034
1035Also, note that the number of watchers usually has a nonlinear effect on
1036overall speed, that is, creating twice as many watchers doesn't take twice
1037the time - usually it takes longer. This puts event loops tested with a
1038higher number of watchers at a disadvantage.
1039
1040To put the range of results into perspective, consider that on the
1041benchmark machine, handling an event takes roughly 1600 CPU cycles with
1042EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU
1043cycles with POE.
963 1044
964C<EV> is the sole leader regarding speed and memory use, which are both 1045C<EV> is the sole leader regarding speed and memory use, which are both
965maximal/minimal, respectively. Even when going through AnyEvent, it uses 1046maximal/minimal, respectively. Even when going through AnyEvent, it uses
966far less memory than any other event loop and is still faster than Event 1047far less memory than any other event loop and is still faster than Event
967natively. 1048natively.
… …
1057 1138
1058=head3 Results 1139=head3 Results
1059 1140
1060 name sockets create request 1141 name sockets create request
1061 EV 20000 69.01 11.16 1142 EV 20000 69.01 11.16
1062 Perl 20000 75.28 112.76 1143 Perl 20000 73.32 35.87
1063 Event 20000 212.62 257.32 1144 Event 20000 212.62 257.32
1064 Glib 20000 651.16 1896.30 1145 Glib 20000 651.16 1896.30
1065 POE 20000 349.67 12317.24 uses POE::Loop::Event 1146 POE 20000 349.67 12317.24 uses POE::Loop::Event
1066 1147
1067=head3 Discussion 1148=head3 Discussion
… …
1113 1194
1114=head3 Results 1195=head3 Results
1115 1196
1116 name sockets create request 1197 name sockets create request
1117 EV 16 20.00 6.54 1198 EV 16 20.00 6.54
1199 Perl 16 25.75 12.62
1118 Event 16 81.27 35.86 1200 Event 16 81.27 35.86
1119 Glib 16 32.63 15.48 1201 Glib 16 32.63 15.48
1120 Perl 16 24.62 162.37
1121 POE 16 261.87 276.28 uses POE::Loop::Event 1202 POE 16 261.87 276.28 uses POE::Loop::Event
1122 1203
1123=head3 Discussion 1204=head3 Discussion
1124 1205
1125The benchmark tries to test the performance of a typical small 1206The benchmark tries to test the performance of a typical small
1126server. While knowing how various event loops perform is interesting, keep 1207server. While knowing how various event loops perform is interesting, keep
1127in mind that their overhead in this case is usually not as important, due 1208in mind that their overhead in this case is usually not as important, due
1128to the small absolute number of watchers. 1209to the small absolute number of watchers (that is, you need efficiency and
1210speed most when you have lots of watchers, not when you only have a few of
1211them).
1129 1212
1130EV is again fastest. 1213EV is again fastest.
1131 1214
1132The C-based event loops Event and Glib come in second this time, as the 1215The C-based event loops Event and Glib come in second this time, as the
1133overhead of running an iteration is much smaller in C than in Perl (little 1216overhead of running an iteration is much smaller in C than in Perl (little
1134code to execute in the inner loop, and perl's function calling overhead is 1217code to execute in the inner loop, and perl's function calling overhead is
1135high, and updating all the data structures is costly). 1218high, and updating all the data structures is costly).
1136 1219
1137The pure perl event loop is much slower, but still competitive. 1220The pure perl event loop is much slower, but still competitive.
1138 1221
1139POE also performs much better in this case, but is is stillf ar behind the 1222POE also performs much better in this case, but is is still far behind the
1140others. 1223others.
1141 1224
1142=head3 Summary 1225=head3 Summary
1143 1226
1144=over 4 1227=over 4

Diff Legend

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