… | |
… | |
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 backends directly, here is a benchmark of various supported event |
869 | over the backends directly, here is a benchmark of various supported event |
870 | models natively and with anyevent. The benchmark creates a lot of timers |
870 | models natively and with anyevent. The benchmark creates a lot of timers |
871 | (with a zero timeout) and io watchers (watching STDOUT, a pty, to become |
871 | (with a zero timeout) and io watchers (watching STDOUT, a pty, to become |
872 | writable), lets them fire exactly once and destroys them again. |
872 | writable, which it is), lets them fire exactly once and destroys them |
|
|
873 | again. |
873 | |
874 | |
874 | Explanation of the fields: |
875 | Explanation of the fields: |
875 | |
876 | |
876 | I<watcher> is the number of event watchers created/destroyed. Sicne |
877 | I<watcher> is the number of event watchers created/destroyed. Sicne |
877 | different event models have vastly different performance each backend was |
878 | different event models have vastly different performance each backend was |