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

Comparing libev/README (file contents):
Revision 1.8 by root, Thu Nov 1 11:55:54 2007 UTC vs.
Revision 1.14 by root, Thu Nov 8 16:58:00 2007 UTC

1libev is modelled (very losely) after libevent 1libev is a high-performance event loop/event model with lots of features.
2(http://monkey.org/~provos/libevent/), but aims to be faster and more
3correct, and also more featureful. Examples:
4 2
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
7DIFFERENCES AND COMPARISON TO LIBEVENT:
8
5(comparisons relative to libevent-1.3e and libev-0.00) 9(comparisons relative to libevent-1.3e and libev-0.00, see also the benchmark
10at http://libev.schmorp.de/bench.html).
6 11
7- multiple watchers can wait for the same event without deregistering others, 12- multiple watchers can wait for the same event without deregistering others,
8 both for file descriptors as well as signals. 13 both for file descriptors as well as signals.
9 (registering two read events on fd 10 and unregistering one will not 14 (registering two read events on fd 10 and unregistering one will not
10 break the other) 15 break the other).
11 16
12- fork() is supported and can be handled 17- fork() is supported and can be handled
13 (there is no way to recover from a fork when libevent is active) 18 (there is no way to recover from a fork when libevent is active).
14 19
15- timers are handled as a priority queue (important operations are O(1)) 20- timers are handled as a priority queue (important operations are O(1))
16 (libevent uses a much less efficient but more complex red-black tree) 21 (libevent uses a much less efficient but more complex red-black tree).
17 22
18- supports absolute (wallclock-based) timers in addition to relative ones, 23- supports absolute (wallclock-based) timers in addition to relative ones,
19 i.e. can schedule timers to occur after n seconds, or at a specific time. 24 i.e. can schedule timers to occur after n seconds, or at a specific time.
20 25
21- timers can be repeating (both absolute and relative ones) 26- timers can be repeating (both absolute and relative ones).
22 27
23- detects time jumps and adjusts timers 28- detects time jumps and adjusts timers
24 (works for both forward and backward time jumps and also for absolute timers) 29 (works for both forward and backward time jumps and also for absolute timers).
25
26- can correctly remove timers while executing callbacks
27 (libevent doesn't handle this reliably and can crash)
28 30
29- race-free signal processing 31- race-free signal processing
30 (libevent may delay processing signals till after the next event) 32 (libevent may delay processing signals till after the next event).
31 33
32- less calls to epoll_ctl 34- less calls to epoll_ctl
33 (stopping and starting an io watcher between two loop iterations will now 35 (stopping and starting an io watcher between two loop iterations will now
34 result in spuriois epoll_ctl calls) 36 result in spuriois epoll_ctl calls).
35 37
36- usually less calls to gettimeofday and clock_gettime 38- usually less calls to gettimeofday and clock_gettime
37 (libevent calls it on every timer event change, libev twice per iteration) 39 (libevent calls it on every timer event change, libev twice per iteration).
38 40
39- watchers use less memory 41- watchers use less memory
40 (libevent on amd64: 152 bytes, libev: <= 56 bytes) 42 (libevent on amd64: 152 bytes, libev: <= 56 bytes).
41 43
42- library uses less memory 44- library uses less memory
43 (libevent allocates large data structures wether used or not, libev 45 (libevent allocates large data structures wether used or not, libev
44 scales all its data structures dynamically) 46 scales all its data structures dynamically).
45 47
46- no hardcoded arbitrary limits 48- no hardcoded arbitrary limits
47 (libevent contains an off-by-one bug and sometimes hardcodes a limit of 49 (libevent contains an off-by-one bug and sometimes hardcodes a limit of
48 32000 fds) 50 32000 fds).
49 51
50- libev separates timer, signal and io watchers from each other 52- libev separates timer, signal and io watchers from each other
51 (libevent combines them, but with libev you can combine them yourself 53 (libevent combines them, but with libev you can combine them yourself
52 by reusing the same callback and still save memory) 54 by reusing the same callback and still save memory).
53 55
54- simpler design, backends are potentially much simpler 56- simpler design, backends are potentially much simpler
55 (in libevent, backends have to deal with watchers, thus the problems) 57 (in libevent, backends have to deal with watchers, thus the problems)
56 (epoll backend in libevent: 366 lines, libev: 90 lines, and more features) 58 (epoll backend in libevent: 366 lines, libev: 90 lines, and more features).
57 59
58- libev handles EBADF gracefully by removing the offending fds. 60- libev handles EBADF gracefully by removing the offending fds.
59 61
60- doesn't rely on nonportable BSD header files. 62- doesn't rely on nonportable BSD header files.
61 63
64- a event.h compatibility header exists, and can be used to run a wide
65 range of libevent programs unchanged (such as evdns.c).
66
67- win32 compatibility for the core parts.
68
69- the event core library (ev and event layer) compiles and works both as
70 C and C++.
71
62whats missing? 72whats missing?
63 73
64- evdns, evhttp, bufferevent are missing, libev is only an even library at 74- no event-like priority support at the moment (the ev priorities
65 the moment. 75 are not yet finished and work differently, but you cna use idle watchers
76 to get a similar effect).
66 77
67- no priority support at the moment
68 78
69- kqueue, poll (libev currently implements epoll and select)
70
71- windows support (whats windows?)
72

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines