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.79 by root, Fri Apr 25 09:08:16 2008 UTC vs.
Revision 1.81 by root, Fri Apr 25 13:05:17 2008 UTC

80module. 80module.
81 81
82During the first call of any watcher-creation method, the module tries 82During the first call of any watcher-creation method, the module tries
83to detect the currently loaded event loop by probing whether one of the 83to detect the currently loaded event loop by probing whether one of the
84following modules is already loaded: L<Coro::EV>, L<Coro::Event>, L<EV>, 84following modules is already loaded: L<Coro::EV>, L<Coro::Event>, L<EV>,
85L<Event>, L<Glib>, L<Tk>, L<AnyEvent::Impl::Perl>, L<Event::Lib>, L<Qt>, 85L<Event>, L<Glib>, L<AnyEvent::Impl::Perl>, L<Tk>, L<Event::Lib>, L<Qt>,
86L<POE>. The first one found is used. If none are found, the module tries 86L<POE>. The first one found is used. If none are found, the module tries
87to load these modules (excluding Event::Lib, Qt and POE as the pure perl 87to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl
88adaptor should always succeed) in the order given. The first one that can 88adaptor should always succeed) in the order given. The first one that can
89be successfully loaded will be used. If, after this, still none could be 89be successfully loaded will be used. If, after this, still none could be
90found, AnyEvent will fall back to a pure-perl event loop, which is not 90found, AnyEvent will fall back to a pure-perl event loop, which is not
91very efficient, but should work everywhere. 91very efficient, but should work everywhere.
92 92
359 AnyEvent::Impl::CoroEV based on Coro::EV, best choice. 359 AnyEvent::Impl::CoroEV based on Coro::EV, best choice.
360 AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice. 360 AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.
361 AnyEvent::Impl::EV based on EV (an interface to libev, best choice). 361 AnyEvent::Impl::EV based on EV (an interface to libev, best choice).
362 AnyEvent::Impl::Event based on Event, second best choice. 362 AnyEvent::Impl::Event based on Event, second best choice.
363 AnyEvent::Impl::Glib based on Glib, third-best choice. 363 AnyEvent::Impl::Glib based on Glib, third-best choice.
364 AnyEvent::Impl::Perl pure-perl implementation, inefficient but portable.
364 AnyEvent::Impl::Tk based on Tk, very bad choice. 365 AnyEvent::Impl::Tk based on Tk, very bad choice.
365 AnyEvent::Impl::Perl pure-perl implementation, inefficient but portable.
366 AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs). 366 AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs).
367 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. 367 AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
368 AnyEvent::Impl::POE based on POE, not generic enough for full support. 368 AnyEvent::Impl::POE based on POE, not generic enough for full support.
369 369
370There is no support for WxWidgets, as WxWidgets has no support for 370There is no support for WxWidgets, as WxWidgets has no support for
921=head2 Discussion 921=head2 Discussion
922 922
923The benchmark does I<not> measure scalability of the event loop very 923The benchmark does I<not> measure scalability of the event loop very
924well. For example, a select-based event loop (such as the pure perl one) 924well. For example, a select-based event loop (such as the pure perl one)
925can never compete with an event loop that uses epoll when the number of 925can never compete with an event loop that uses epoll when the number of
926file descriptors grows high. In this benchmark, only a single filehandle 926file descriptors grows high. In this benchmark, all events become ready at
927is used (although some of the AnyEvent adaptors dup() its file descriptor 927the same time, so select/poll-based implementations get an unnatural speed
928to worka round bugs). 928boost.
929 929
930C<EV> is the sole leader regarding speed and memory use, which are both 930C<EV> is the sole leader regarding speed and memory use, which are both
931maximal/minimal, respectively. Even when going through AnyEvent, there are 931maximal/minimal, respectively. Even when going through AnyEvent, there are
932only two event loops that use slightly less memory (the C<Event> module 932only two event loops that use slightly less memory (the C<Event> module
933natively and the pure perl backend), and no faster event models, not even 933natively and the pure perl backend), and no faster event models, not even

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines