… | |
… | |
136 | |
136 | |
137 | Note that C<my $w; $w => combination. This is necessary because in Perl, |
137 | Note that C<my $w; $w => combination. This is necessary because in Perl, |
138 | my variables are only visible after the statement in which they are |
138 | my variables are only visible after the statement in which they are |
139 | declared. |
139 | declared. |
140 | |
140 | |
141 | =head2 IO WATCHERS |
141 | =head2 I/O WATCHERS |
142 | |
142 | |
143 | You can create an I/O watcher by calling the C<< AnyEvent->io >> method |
143 | You can create an I/O watcher by calling the C<< AnyEvent->io >> method |
144 | with the following mandatory key-value pairs as arguments: |
144 | with the following mandatory key-value pairs as arguments: |
145 | |
145 | |
146 | C<fh> the Perl I<file handle> (I<not> file descriptor) to watch for |
146 | C<fh> the Perl I<file handle> (I<not> file descriptor) to watch for |
… | |
… | |
706 | |
706 | |
707 | =back |
707 | =back |
708 | |
708 | |
709 | =head1 EXAMPLE PROGRAM |
709 | =head1 EXAMPLE PROGRAM |
710 | |
710 | |
711 | The following program uses an IO watcher to read data from STDIN, a timer |
711 | The following program uses an I/O watcher to read data from STDIN, a timer |
712 | to display a message once per second, and a condition variable to quit the |
712 | to display a message once per second, and a condition variable to quit the |
713 | program when the user enters quit: |
713 | program when the user enters quit: |
714 | |
714 | |
715 | use AnyEvent; |
715 | use AnyEvent; |
716 | |
716 | |
… | |
… | |
867 | |
867 | |
868 | To give you an idea of the performance and overheads that AnyEvent adds |
868 | To give you an idea of the performance and overheads that AnyEvent adds |
869 | over the event loops themselves (and to give you an impression of the |
869 | over the event loops themselves (and to give you an impression of the |
870 | speed of various event loops), here is a benchmark of various supported |
870 | speed of various event loops), here is a benchmark of various supported |
871 | event models natively and with anyevent. The benchmark creates a lot of |
871 | event models natively and with anyevent. The benchmark creates a lot of |
872 | timers (with a zero timeout) and io watchers (watching STDOUT, a pty, to |
872 | timers (with a zero timeout) and I/O watchers (watching STDOUT, a pty, to |
873 | become writable, which it is), lets them fire exactly once and destroys |
873 | become writable, which it is), lets them fire exactly once and destroys |
874 | them again. |
874 | them again. |
|
|
875 | |
|
|
876 | Rewriting the benchmark to use many different sockets instead of using |
|
|
877 | the same filehandle for all I/O watchers results in a much longer runtime |
|
|
878 | (socket creation is expensive), but qualitatively the same figures, so it |
|
|
879 | was not used. |
875 | |
880 | |
876 | =head2 Explanation of the columns |
881 | =head2 Explanation of the columns |
877 | |
882 | |
878 | I<watcher> is the number of event watchers created/destroyed. Since |
883 | I<watcher> is the number of event watchers created/destroyed. Since |
879 | different event models feature vastly different performances, each event |
884 | different event models feature vastly different performances, each event |
… | |
… | |
928 | natively and the pure perl backend), and no faster event models, not even |
933 | natively and the pure perl backend), and no faster event models, not even |
929 | C<Event> natively. |
934 | C<Event> natively. |
930 | |
935 | |
931 | The pure perl implementation is hit in a few sweet spots (both the |
936 | The pure perl implementation is hit in a few sweet spots (both the |
932 | zero timeout and the use of a single fd hit optimisations in the perl |
937 | zero timeout and the use of a single fd hit optimisations in the perl |
933 | interpreter and the backend itself). Nevertheless tis shows that it |
938 | interpreter and the backend itself, and all watchers become ready at the |
934 | adds very little overhead in itself. Like any select-based backend its |
939 | same time). Nevertheless this shows that it adds very little overhead in |
935 | performance becomes really bad with lots of file descriptors, of course, |
940 | itself. Like any select-based backend its performance becomes really bad |
|
|
941 | with lots of file descriptors (and few of them active), of course, but |
936 | but this was not subject of this benchmark. |
942 | this was not subject of this benchmark. |
937 | |
943 | |
938 | The C<Event> module has a relatively high setup and callback invocation cost, |
944 | The C<Event> module has a relatively high setup and callback invocation cost, |
939 | but overall scores on the third place. |
945 | but overall scores on the third place. |
940 | |
946 | |
941 | C<Glib>'s memory usage is quite a bit bit higher, but it features a |
947 | C<Glib>'s memory usage is quite a bit bit higher, but it features a |
… | |
… | |
956 | |
962 | |
957 | C<POE>, regardless of underlying event loop (wether using its pure perl |
963 | C<POE>, regardless of underlying event loop (wether using its pure perl |
958 | select-based backend or the Event module) shows abysmal performance and |
964 | select-based backend or the Event module) shows abysmal performance and |
959 | memory usage: Watchers use almost 30 times as much memory as EV watchers, |
965 | memory usage: Watchers use almost 30 times as much memory as EV watchers, |
960 | and 10 times as much memory as both Event or EV via AnyEvent. Watcher |
966 | and 10 times as much memory as both Event or EV via AnyEvent. Watcher |
961 | invocation is almost 700 times slower than with AnyEvent's pure perl |
967 | invocation is almost 900 times slower than with AnyEvent's pure perl |
962 | implementation. The design of the POE adaptor class in AnyEvent can not |
968 | implementation. The design of the POE adaptor class in AnyEvent can not |
963 | really account for this, as session creation overhead is small compared |
969 | really account for this, as session creation overhead is small compared |
964 | to execution of the state machine, which is coded pretty optimally within |
970 | to execution of the state machine, which is coded pretty optimally within |
965 | L<AnyEvent::Impl::POE>. POE simply seems to be abysmally slow. |
971 | L<AnyEvent::Impl::POE>. POE simply seems to be abysmally slow. |
966 | |
972 | |