ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/libev/README
(Generate patch)

Comparing libev/README (file contents):
Revision 1.11 by root, Fri Nov 2 15:56:19 2007 UTC vs.
Revision 1.22 by root, Sun Jun 23 19:22:35 2019 UTC

1libev is a high-performance event loop/event model with lots of features. 1libev is a high-performance event loop/event model with lots of features.
2(see benchmark at http://libev.schmorp.de/bench.html)
2 3
3It is modelled (very losely) after libevent
4(http://monkey.org/~provos/libevent/) and the Event perl module, but aims
5to be faster and more correct, and also more featureful.
6 4
7DIFFERENCES AND COMPARISON TO LIBEVENT: 5ABOUT
8 6
9(comparisons relative to libevent-1.3e and libev-0.00, see also the benchmark 7 Homepage: http://software.schmorp.de/pkg/libev
10at http://libev.schmorp.de/bench.html). 8 Mailinglist: libev@lists.schmorp.de
9 http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
10 Library Documentation: http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod
11 11
12- multiple watchers can wait for the same event without deregistering others, 12 Libev is modelled (very losely) after libevent and the Event perl
13 both for file descriptors as well as signals. 13 module, but is faster, scales better and is more correct, and also more
14 (registering two read events on fd 10 and unregistering one will not 14 featureful. And also smaller. Yay.
15 break the other).
16 15
17- fork() is supported and can be handled 16 Some of the specialties of libev not commonly found elsewhere are:
18 (there is no way to recover from a fork when libevent is active). 17
18 - extensive and detailed, readable documentation (not doxygen garbage).
19 - fully supports fork, can detect fork in various ways and automatically
20 re-arms kernel mechanisms that do not support fork.
21 - highly optimised select, poll, linux epoll, linux aio, bsd kqueue
22 and solaris event ports backends.
23 - filesystem object (path) watching (with optional linux inotify support).
24 - wallclock-based times (using absolute time, cron-like).
25 - relative timers/timeouts (handle time jumps).
26 - fast intra-thread communication between multiple
27 event loops (with optional fast linux eventfd backend).
28 - extremely easy to embed (fully documented, no dependencies,
29 autoconf supported but optional).
30 - very small codebase, no bloated library, simple code.
31 - fully extensible by being able to plug into the event loop,
32 integrate other event loops, integrate other event loop users.
33 - very little memory use (small watchers, small event loop data).
34 - optional C++ interface allowing method and function callbacks
35 at no extra memory or runtime overhead.
36 - optional Perl interface with similar characteristics (capable
37 of running Glib/Gtk2 on libev).
38 - support for other languages (multiple C++ interfaces, D, Ruby,
39 Python) available from third-parties.
19 40
20- timers are handled as a priority queue (important operations are O(1)) 41 Examples of programs that embed libev: the EV perl module, node.js,
21 (libevent uses a much less efficient but more complex red-black tree). 42 auditd, rxvt-unicode, gvpe (GNU Virtual Private Ethernet), the
43 Deliantra MMORPG server (http://www.deliantra.net/), Rubinius (a
44 next-generation Ruby VM), the Ebb web server, the Rev event toolkit.
22 45
23- supports absolute (wallclock-based) timers in addition to relative ones,
24 i.e. can schedule timers to occur after n seconds, or at a specific time.
25 46
26- timers can be repeating (both absolute and relative ones). 47CONTRIBUTORS
27 48
28- detects time jumps and adjusts timers 49 libev was written and designed by Marc Lehmann and Emanuele Giaquinta.
29 (works for both forward and backward time jumps and also for absolute timers).
30 50
31- can correctly remove timers while executing callbacks 51 The following people sent in patches or made other noteworthy
32 (libevent doesn't handle this reliably and can crash). 52 contributions to the design (for minor patches, see the Changes
53 file. If I forgot to include you, please shout at me, it was an
54 accident):
33 55
34- race-free signal processing 56 W.C.A. Wijngaards
35 (libevent may delay processing signals till after the next event). 57 Christopher Layne
58 Chris Brody
36 59
37- less calls to epoll_ctl
38 (stopping and starting an io watcher between two loop iterations will now
39 result in spuriois epoll_ctl calls).
40
41- usually less calls to gettimeofday and clock_gettime
42 (libevent calls it on every timer event change, libev twice per iteration).
43
44- watchers use less memory
45 (libevent on amd64: 152 bytes, libev: <= 56 bytes).
46
47- library uses less memory
48 (libevent allocates large data structures wether used or not, libev
49 scales all its data structures dynamically).
50
51- no hardcoded arbitrary limits
52 (libevent contains an off-by-one bug and sometimes hardcodes a limit of
53 32000 fds).
54
55- libev separates timer, signal and io watchers from each other
56 (libevent combines them, but with libev you can combine them yourself
57 by reusing the same callback and still save memory).
58
59- simpler design, backends are potentially much simpler
60 (in libevent, backends have to deal with watchers, thus the problems)
61 (epoll backend in libevent: 366 lines, libev: 90 lines, and more features).
62
63- libev handles EBADF gracefully by removing the offending fds.
64
65- doesn't rely on nonportable BSD header files.
66
67- a event.h compatibility header exists, and can be used to run a wide
68 range of libevent programs unchanged (such as evdns.c).
69
70whats missing?
71
72- evbuffer, evhttp, bufferevent are missing.
73
74- no priority support at the moment (but likely to be delivered later).
75
76- kqueue, poll (libev currently implements epoll and select).
77
78- windows support (whats windows?).
79

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines