| … | |
… | |
| 962 | |
962 | |
| 963 | 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 |
| 964 | select-based backend or the Event module) shows abysmal performance and |
964 | select-based backend or the Event module) shows abysmal performance and |
| 965 | 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, |
| 966 | 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 |
| 967 | 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 |
| 968 | 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 |
| 969 | really account for this, as session creation overhead is small compared |
969 | really account for this, as session creation overhead is small compared |
| 970 | 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 |
| 971 | L<AnyEvent::Impl::POE>. POE simply seems to be abysmally slow. |
971 | L<AnyEvent::Impl::POE>. POE simply seems to be abysmally slow. |
| 972 | |
972 | |
