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.95 by root, Sat Apr 26 11:06:45 2008 UTC vs.
Revision 1.102 by root, Sun Apr 27 21:16:26 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
… …
963 1034
964Also, note that the number of watchers usually has a nonlinear effect on 1035Also, note that the number of watchers usually has a nonlinear effect on
965overall speed, that is, creating twice as many watchers doesn't take twice 1036overall speed, that is, creating twice as many watchers doesn't take twice
966the time - usually it takes longer. This puts event loops tested with a 1037the time - usually it takes longer. This puts event loops tested with a
967higher number of watchers at a disadvantage. 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.
968 1044
969C<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
970maximal/minimal, respectively. Even when going through AnyEvent, it uses 1046maximal/minimal, respectively. Even when going through AnyEvent, it uses
971far 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
972natively. 1048natively.
… …
1062 1138
1063=head3 Results 1139=head3 Results
1064 1140
1065 name sockets create request 1141 name sockets create request
1066 EV 20000 69.01 11.16 1142 EV 20000 69.01 11.16
1067 Perl 20000 75.28 112.76 1143 Perl 20000 73.32 35.87
1068 Event 20000 212.62 257.32 1144 Event 20000 212.62 257.32
1069 Glib 20000 651.16 1896.30 1145 Glib 20000 651.16 1896.30
1070 POE 20000 349.67 12317.24 uses POE::Loop::Event 1146 POE 20000 349.67 12317.24 uses POE::Loop::Event
1071 1147
1072=head3 Discussion 1148=head3 Discussion
… …
1118 1194
1119=head3 Results 1195=head3 Results
1120 1196
1121 name sockets create request 1197 name sockets create request
1122 EV 16 20.00 6.54 1198 EV 16 20.00 6.54
1199 Perl 16 25.75 12.62
1123 Event 16 81.27 35.86 1200 Event 16 81.27 35.86
1124 Glib 16 32.63 15.48 1201 Glib 16 32.63 15.48
1125 Perl 16 24.62 162.37
1126 POE 16 261.87 276.28 uses POE::Loop::Event 1202 POE 16 261.87 276.28 uses POE::Loop::Event
1127 1203
1128=head3 Discussion 1204=head3 Discussion
1129 1205
1130The benchmark tries to test the performance of a typical small 1206The benchmark tries to test the performance of a typical small
1131server. While knowing how various event loops perform is interesting, keep 1207server. While knowing how various event loops perform is interesting, keep
1132in 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
1133to 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).
1134 1212
1135EV is again fastest. 1213EV is again fastest.
1136 1214
1137The C-based event loops Event and Glib come in second this time, as the 1215Perl again comes second. It is noticably faster than the C-based event
1138overhead of running an iteration is much smaller in C than in Perl (little 1216loops Event and Glib, although the difference is too small to really
1139code to execute in the inner loop, and perl's function calling overhead is 1217matter.
1140high, and updating all the data structures is costly).
1141 1218
1142The pure perl event loop is much slower, but still competitive.
1143
1144POE also performs much better in this case, but is is stillf ar behind the 1219POE also performs much better in this case, but is is still far behind the
1145others. 1220others.
1146 1221
1147=head3 Summary 1222=head3 Summary
1148 1223
1149=over 4 1224=over 4

Diff Legend

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