[ViewVC] Diff of: cvs/AnyEvent/lib/AnyEvent.pm

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.64 by root, Fri Apr 25 06:54:08 2008 UTC vs.
Revision 1.96 by root, Sat Apr 26 11:16:16 2008 UTC

…		…
80	module.	80	module.
81		81
82	During the first call of any watcher-creation method, the module tries	82	During the first call of any watcher-creation method, the module tries
83	to detect the currently loaded event loop by probing whether one of the	83	to detect the currently loaded event loop by probing whether one of the
84	following modules is already loaded: L<Coro::EV>, L<Coro::Event>, L<EV>,	84	following modules is already loaded: L<Coro::EV>, L<Coro::Event>, L<EV>,
85	L<Event>, L<Glib>, L<Tk>, L<AnyEvent::Impl::Perl>, L<Event::Lib>, L<Qt>,	85	L<Event>, L<Glib>, L<AnyEvent::Impl::Perl>, L<Tk>, L<Event::Lib>, L<Qt>,
86	L<POE>. The first one found is used. If none are found, the module tries	86	L<POE>. The first one found is used. If none are found, the module tries
87	to load these modules (excluding Event::Lib, Qt and POE as the pure perl	87	to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl
88	adaptor should always succeed) in the order given. The first one that can	88	adaptor should always succeed) in the order given. The first one that can
89	be successfully loaded will be used. If, after this, still none could be	89	be successfully loaded will be used. If, after this, still none could be
90	found, AnyEvent will fall back to a pure-perl event loop, which is not	90	found, AnyEvent will fall back to a pure-perl event loop, which is not
91	very efficient, but should work everywhere.	91	very efficient, but should work everywhere.
92		92
…		…
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
147	events. C<poll> must be a string that is either C<r> or C<w>, which	147	for events. C<poll> must be a string that is either C<r> or C<w>,
148	creates a watcher waiting for "r"eadable or "w"ritable events,	148	which creates a watcher waiting for "r"eadable or "w"ritable events,
149	respectively. C<cb> is the callback to invoke each time the file handle	149	respectively. C<cb> is the callback to invoke each time the file handle
150	becomes ready.	150	becomes ready.
151		151
152	As long as the I/O watcher exists it will keep the file descriptor or a	152	Although the callback might get passed parameters, their value and
153	copy of it alive/open.	153	presence is undefined and you cannot rely on them. Portable AnyEvent
		154	callbacks cannot use arguments passed to I/O watcher callbacks.
154		155
		156	The I/O watcher might use the underlying file descriptor or a copy of it.
155	It is not allowed to close a file handle as long as any watcher is active	157	You must not close a file handle as long as any watcher is active on the
156	on the underlying file descriptor.	158	underlying file descriptor.
157		159
158	Some event loops issue spurious readyness notifications, so you should	160	Some event loops issue spurious readyness notifications, so you should
159	always use non-blocking calls when reading/writing from/to your file	161	always use non-blocking calls when reading/writing from/to your file
160	handles.	162	handles.
161		163
…		…
172		174
173	You can create a time watcher by calling the C<< AnyEvent->timer >>	175	You can create a time watcher by calling the C<< AnyEvent->timer >>
174	method with the following mandatory arguments:	176	method with the following mandatory arguments:
175		177
176	C<after> specifies after how many seconds (fractional values are	178	C<after> specifies after how many seconds (fractional values are
177	supported) should the timer activate. C<cb> the callback to invoke in that	179	supported) the callback should be invoked. C<cb> is the callback to invoke
178	case.	180	in that case.
		181
		182	Although the callback might get passed parameters, their value and
		183	presence is undefined and you cannot rely on them. Portable AnyEvent
		184	callbacks cannot use arguments passed to time watcher callbacks.
179		185
180	The timer callback will be invoked at most once: if you want a repeating	186	The timer callback will be invoked at most once: if you want a repeating
181	timer you have to create a new watcher (this is a limitation by both Tk	187	timer you have to create a new watcher (this is a limitation by both Tk
182	and Glib).	188	and Glib).
183		189
…		…
228		234
229	You can watch for signals using a signal watcher, C<signal> is the signal	235	You can watch for signals using a signal watcher, C<signal> is the signal
230	I<name> without any C<SIG> prefix, C<cb> is the Perl callback to	236	I<name> without any C<SIG> prefix, C<cb> is the Perl callback to
231	be invoked whenever a signal occurs.	237	be invoked whenever a signal occurs.
232		238
		239	Although the callback might get passed parameters, their value and
		240	presence is undefined and you cannot rely on them. Portable AnyEvent
		241	callbacks cannot use arguments passed to signal watcher callbacks.
		242
233	Multiple signal occurances can be clumped together into one callback	243	Multiple signal occurances can be clumped together into one callback
234	invocation, and callback invocation will be synchronous. synchronous means	244	invocation, and callback invocation will be synchronous. synchronous means
235	that it might take a while until the signal gets handled by the process,	245	that it might take a while until the signal gets handled by the process,
236	but it is guarenteed not to interrupt any other callbacks.	246	but it is guarenteed not to interrupt any other callbacks.
237		247
…		…
251		261
252	The child process is specified by the C<pid> argument (if set to C<0>, it	262	The child process is specified by the C<pid> argument (if set to C<0>, it
253	watches for any child process exit). The watcher will trigger as often	263	watches for any child process exit). The watcher will trigger as often
254	as status change for the child are received. This works by installing a	264	as status change for the child are received. This works by installing a
255	signal handler for C<SIGCHLD>. The callback will be called with the pid	265	signal handler for C<SIGCHLD>. The callback will be called with the pid
256	and exit status (as returned by waitpid).	266	and exit status (as returned by waitpid), so unlike other watcher types,
		267	you I<can> rely on child watcher callback arguments.
257		268
258	Example: wait for pid 1333	269	There is a slight catch to child watchers, however: you usually start them
		270	I<after> the child process was created, and this means the process could
		271	have exited already (and no SIGCHLD will be sent anymore).
		272
		273	Not all event models handle this correctly (POE doesn't), but even for
		274	event models that I<do> handle this correctly, they usually need to be
		275	loaded before the process exits (i.e. before you fork in the first place).
		276
		277	This means you cannot create a child watcher as the very first thing in an
		278	AnyEvent program, you I<have> to create at least one watcher before you
		279	C<fork> the child (alternatively, you can call C<AnyEvent::detect>).
		280
		281	Example: fork a process and wait for it
		282
		283	my $done = AnyEvent->condvar;
		284
		285	AnyEvent::detect; # force event module to be initialised
		286
		287	my $pid = fork or exit 5;
259		288
260	my $w = AnyEvent->child (	289	my $w = AnyEvent->child (
261	pid => 1333,	290	pid => $pid,
262	cb => sub {	291	cb => sub {
263	my ($pid, $status) = @_;	292	my ($pid, $status) = @_;
264	warn "pid $pid exited with status $status";	293	warn "pid $pid exited with status $status";
		294	$done->broadcast;
265	},	295	},
266	);	296	);
		297
		298	# do something else, then wait for process exit
		299	$done->wait;
267		300
268	=head2 CONDITION VARIABLES	301	=head2 CONDITION VARIABLES
269		302
270	Condition variables can be created by calling the C<< AnyEvent->condvar >>	303	Condition variables can be created by calling the C<< AnyEvent->condvar >>
271	method without any arguments.	304	method without any arguments.
…		…
359	AnyEvent::Impl::CoroEV based on Coro::EV, best choice.	392	AnyEvent::Impl::CoroEV based on Coro::EV, best choice.
360	AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.	393	AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.
361	AnyEvent::Impl::EV based on EV (an interface to libev, best choice).	394	AnyEvent::Impl::EV based on EV (an interface to libev, best choice).
362	AnyEvent::Impl::Event based on Event, second best choice.	395	AnyEvent::Impl::Event based on Event, second best choice.
363	AnyEvent::Impl::Glib based on Glib, third-best choice.	396	AnyEvent::Impl::Glib based on Glib, third-best choice.
		397	AnyEvent::Impl::Perl pure-perl implementation, inefficient but portable.
364	AnyEvent::Impl::Tk based on Tk, very bad choice.	398	AnyEvent::Impl::Tk based on Tk, very bad choice.
365	AnyEvent::Impl::Perl pure-perl implementation, inefficient but portable.
366	AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs).	399	AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs).
367	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.	400	AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse.
368	AnyEvent::Impl::POE based on POE, not generic enough for full support.	401	AnyEvent::Impl::POE based on POE, not generic enough for full support.
369		402
370	There is no support for WxWidgets, as WxWidgets has no support for	403	There is no support for WxWidgets, as WxWidgets has no support for
…		…
706		739
707	=back	740	=back
708		741
709	=head1 EXAMPLE PROGRAM	742	=head1 EXAMPLE PROGRAM
710		743
711	The following program uses an IO watcher to read data from STDIN, a timer	744	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	745	to display a message once per second, and a condition variable to quit the
713	program when the user enters quit:	746	program when the user enters quit:
714		747
715	use AnyEvent;	748	use AnyEvent;
716		749
…		…
861	});	894	});
862		895
863	$quit->wait;	896	$quit->wait;
864		897
865		898
866	=head1 BENCHMARK	899	=head1 BENCHMARKS
867		900
868	To give you an idea of the performance an doverheads that AnyEvent adds	901	To give you an idea of the performance and overheads that AnyEvent adds
869	over the backends, here is a benchmark of various supported backends. The	902	over the event loops themselves and to give you an impression of the speed
870	benchmark creates a lot of timers (with zero timeout) and io events	903	of various event loops I prepared some benchmarks.
871	(watching STDOUT, a pty, to become writable).
872		904
873	Explanation of the fields:	905	=head2 BENCHMARKING ANYEVENT OVERHEAD
874		906
		907	Here is a benchmark of various supported event models used natively and
		908	through anyevent. The benchmark creates a lot of timers (with a zero
		909	timeout) and I/O watchers (watching STDOUT, a pty, to become writable,
		910	which it is), lets them fire exactly once and destroys them again.
		911
		912	Source code for this benchmark is found as F<eg/bench> in the AnyEvent
		913	distribution.
		914
		915	=head3 Explanation of the columns
		916
875	I<watcher> is the number of event watchers created/destroyed. Sicne	917	I<watcher> is the number of event watchers created/destroyed. Since
876	different event models have vastly different performance each backend was	918	different event models feature vastly different performances, each event
877	handed a number of watchers so that overall runtime is acceptable and	919	loop was given a number of watchers so that overall runtime is acceptable
878	similar to all backends (and keep them from crashing).	920	and similar between tested event loop (and keep them from crashing): Glib
		921	would probably take thousands of years if asked to process the same number
		922	of watchers as EV in this benchmark.
879		923
880	I<bytes> is the number of bytes (as measured by resident set size) used by	924	I<bytes> is the number of bytes (as measured by the resident set size,
881	each watcher.	925	RSS) consumed by each watcher. This method of measuring captures both C
		926	and Perl-based overheads.
882		927
883	I<create> is the time, in microseconds, to create a single watcher.	928	I<create> is the time, in microseconds (millionths of seconds), that it
		929	takes to create a single watcher. The callback is a closure shared between
		930	all watchers, to avoid adding memory overhead. That means closure creation
		931	and memory usage is not included in the figures.
884		932
885	I<invoke> is the time, in microseconds, used to invoke a simple callback	933	I<invoke> is the time, in microseconds, used to invoke a simple
886	that simply counts down.	934	callback. The callback simply counts down a Perl variable and after it was
		935	invoked "watcher" times, it would C<< ->broadcast >> a condvar once to
		936	signal the end of this phase.
887		937
888	I<destroy> is the time, in microseconds, to destroy a single watcher.	938	I<destroy> is the time, in microseconds, that it takes to destroy a single
		939	watcher.
889		940
		941	=head3 Results
		942
890	name watcher bytes create invoke destroy comment	943	name watchers bytes create invoke destroy comment
891	EV/EV 400000 244 0.56 0.46 0.31 EV native interface	944	EV/EV 400000 244 0.56 0.46 0.31 EV native interface
892	EV/Any 100000 610 3.52 0.91 0.75	945	EV/Any 100000 244 2.50 0.46 0.29 EV + AnyEvent watchers
893	CoroEV/Any 100000 610 3.49 0.92 0.75 coroutines + Coro::Signal	946	CoroEV/Any 100000 244 2.49 0.44 0.29 coroutines + Coro::Signal
894	Perl/Any 10000 654 4.64 1.22 0.77 pure perl implementation	947	Perl/Any 100000 513 4.92 0.87 1.12 pure perl implementation
895	Event/Event 10000 523 28.05 21.38 5.22 Event native interface	948	Event/Event 16000 516 31.88 31.30 0.85 Event native interface
896	Event/Any 10000 943 34.43 20.48 1.39	949	Event/Any 16000 936 39.17 33.63 1.43 Event + AnyEvent watchers
897	Glib/Any 16000 1357 96.99 12.55 55.51 quadratic behaviour	950	Glib/Any 16000 1357 98.22 12.41 54.00 quadratic behaviour
898	Tk/Any 2000 1855 27.01 66.61 14.03 SEGV with >> 2000 watchers	951	Tk/Any 2000 1860 26.97 67.98 14.00 SEGV with >> 2000 watchers
899	POE/Select 2000 6343 94.69 807.65 562.69 POE::Loop::Select
900	POE/Event 2000 6644 108.15 768.19 14.33 POE::Loop::Event	952	POE/Event 2000 6644 108.64 736.02 14.73 via POE::Loop::Event
		953	POE/Select 2000 6343 94.13 809.12 565.96 via POE::Loop::Select
901		954
902	Discussion: The benchmark does I<not> bench scalability of the	955	=head3 Discussion
		956
		957	The benchmark does I<not> measure scalability of the event loop very
903	backend. For example a select-based backend (such as the pureperl one) can	958	well. For example, a select-based event loop (such as the pure perl one)
904	never compete with a backend using epoll. In this benchmark, only a single	959	can never compete with an event loop that uses epoll when the number of
905	filehandle is used.	960	file descriptors grows high. In this benchmark, all events become ready at
		961	the same time, so select/poll-based implementations get an unnatural speed
		962	boost.
906		963
		964	Also, note that the number of watchers usually has a nonlinear effect on
		965	overall speed, that is, creating twice as many watchers doesn't take twice
		966	the time - usually it takes longer. This puts event loops tested with a
		967	higher number of watchers at a disadvantage.
		968
		969	To put the range of results into perspective, consider that on the
		970	benchmark machine, handling an event takes roughly 1600 CPU cycles with
		971	EV, 3100 CPU cycles with AnyEvent's pure perl loop and almost 3000000 CPU
		972	cycles with POE.
		973
907	EV is the sole leader regarding speed and memory use, which are both	974	C<EV> is the sole leader regarding speed and memory use, which are both
908	maximal/minimal. Even when going through AnyEvent, there is only one event	975	maximal/minimal, respectively. Even when going through AnyEvent, it uses
909	loop that uses less memory (the Event module natively), and no faster	976	far less memory than any other event loop and is still faster than Event
910	event model.	977	natively.
911		978
912	The pure perl implementation is hit in a few sweet spots (both the	979	The pure perl implementation is hit in a few sweet spots (both the
913	zero timeout and the use of a single fd hit optimisations in the perl	980	constant timeout and the use of a single fd hit optimisations in the perl
914	interpreter and the backend itself), but it shows that it adds very little	981	interpreter and the backend itself). Nevertheless this shows that it
915	overhead in itself. Like any select-based backend it's performance becomes	982	adds very little overhead in itself. Like any select-based backend its
916	really bad with lots of file descriptors.	983	performance becomes really bad with lots of file descriptors (and few of
		984	them active), of course, but this was not subject of this benchmark.
917		985
918	The Event module has a relatively high setup and callback invocation cost,	986	The C<Event> module has a relatively high setup and callback invocation
919	but overall scores on the third place.	987	cost, but overall scores in on the third place.
920		988
921	Glib has a little higher memory cost, a bit fster callback invocation and	989	C<Glib>'s memory usage is quite a bit higher, but it features a
922	has a similar speed as Event.	990	faster callback invocation and overall ends up in the same class as
		991	C<Event>. However, Glib scales extremely badly, doubling the number of
		992	watchers increases the processing time by more than a factor of four,
		993	making it completely unusable when using larger numbers of watchers
		994	(note that only a single file descriptor was used in the benchmark, so
		995	inefficiencies of C<poll> do not account for this).
923		996
924	The Tk backend works relatively well, the fact that it crashes with	997	The C<Tk> adaptor works relatively well. The fact that it crashes with
925	more than 2000 watchers is a big setback, however, as correctness takes	998	more than 2000 watchers is a big setback, however, as correctness takes
926	precedence over speed.	999	precedence over speed. Nevertheless, its performance is surprising, as the
		1000	file descriptor is dup()ed for each watcher. This shows that the dup()
		1001	employed by some adaptors is not a big performance issue (it does incur a
		1002	hidden memory cost inside the kernel which is not reflected in the figures
		1003	above).
927		1004
928	POE, regardless of backend (wether it's pure perl select backend or the	1005	C<POE>, regardless of underlying event loop (whether using its pure
929	Event backend) shows abysmal performance and memory usage: Watchers use	1006	perl select-based backend or the Event module, the POE-EV backend
930	almost 30 times as much memory as EV watchers, and 10 times as much memory	1007	couldn't be tested because it wasn't working) shows abysmal performance
931	as both Event or EV via AnyEvent.	1008	and memory usage: Watchers use almost 30 times as much memory as
		1009	EV watchers, and 10 times as much memory as Event (the high memory
		1010	requirements are caused by requiring a session for each watcher). Watcher
		1011	invocation speed is almost 900 times slower than with AnyEvent's pure perl
		1012	implementation. The design of the POE adaptor class in AnyEvent can not
		1013	really account for this, as session creation overhead is small compared
		1014	to execution of the state machine, which is coded pretty optimally within
		1015	L<AnyEvent::Impl::POE>. POE simply seems to be abysmally slow.
932		1016
		1017	=head3 Summary
		1018
		1019	=over 4
		1020
933	Summary: using EV through AnyEvent is faster than any other event	1021	=item * Using EV through AnyEvent is faster than any other event loop
934	loop. The overhead AnyEvent adds can be very small, and you should avoid	1022	(even when used without AnyEvent), but most event loops have acceptable
935	POE like the plague if you want performance or reasonable memory usage.	1023	performance with or without AnyEvent.
		1024
		1025	=item * The overhead AnyEvent adds is usually much smaller than the overhead of
		1026	the actual event loop, only with extremely fast event loops such as EV
		1027	adds AnyEvent significant overhead.
		1028
		1029	=item * You should avoid POE like the plague if you want performance or
		1030	reasonable memory usage.
		1031
		1032	=back
		1033
		1034	=head2 BENCHMARKING THE LARGE SERVER CASE
		1035
		1036	This benchmark atcually benchmarks the event loop itself. It works by
		1037	creating a number of "servers": each server consists of a socketpair, a
		1038	timeout watcher that gets reset on activity (but never fires), and an I/O
		1039	watcher waiting for input on one side of the socket. Each time the socket
		1040	watcher reads a byte it will write that byte to a random other "server".
		1041
		1042	The effect is that there will be a lot of I/O watchers, only part of which
		1043	are active at any one point (so there is a constant number of active
		1044	fds for each loop iterstaion, but which fds these are is random). The
		1045	timeout is reset each time something is read because that reflects how
		1046	most timeouts work (and puts extra pressure on the event loops).
		1047
		1048	In this benchmark, we use 10000 socketpairs (20000 sockets), of which 100
		1049	(1%) are active. This mirrors the activity of large servers with many
		1050	connections, most of which are idle at any one point in time.
		1051
		1052	Source code for this benchmark is found as F<eg/bench2> in the AnyEvent
		1053	distribution.
		1054
		1055	=head3 Explanation of the columns
		1056
		1057	I<sockets> is the number of sockets, and twice the number of "servers" (as
		1058	each server has a read and write socket end).
		1059
		1060	I<create> is the time it takes to create a socketpair (which is
		1061	nontrivial) and two watchers: an I/O watcher and a timeout watcher.
		1062
		1063	I<request>, the most important value, is the time it takes to handle a
		1064	single "request", that is, reading the token from the pipe and forwarding
		1065	it to another server. This includes deleting the old timeout and creating
		1066	a new one that moves the timeout into the future.
		1067
		1068	=head3 Results
		1069
		1070	name sockets create request
		1071	EV 20000 69.01 11.16
		1072	Perl 20000 75.28 112.76
		1073	Event 20000 212.62 257.32
		1074	Glib 20000 651.16 1896.30
		1075	POE 20000 349.67 12317.24 uses POE::Loop::Event
		1076
		1077	=head3 Discussion
		1078
		1079	This benchmark I<does> measure scalability and overall performance of the
		1080	particular event loop.
		1081
		1082	EV is again fastest. Since it is using epoll on my system, the setup time
		1083	is relatively high, though.
		1084
		1085	Perl surprisingly comes second. It is much faster than the C-based event
		1086	loops Event and Glib.
		1087
		1088	Event suffers from high setup time as well (look at its code and you will
		1089	understand why). Callback invocation also has a high overhead compared to
		1090	the C<< $_->() for .. >>-style loop that the Perl event loop uses. Event
		1091	uses select or poll in basically all documented configurations.
		1092
		1093	Glib is hit hard by its quadratic behaviour w.r.t. many watchers. It
		1094	clearly fails to perform with many filehandles or in busy servers.
		1095
		1096	POE is still completely out of the picture, taking over 1000 times as long
		1097	as EV, and over 100 times as long as the Perl implementation, even though
		1098	it uses a C-based event loop in this case.
		1099
		1100	=head3 Summary
		1101
		1102	=over 4
		1103
		1104	=item * The pure perl implementation performs extremely well, considering
		1105	that it uses select.
		1106
		1107	=item * Avoid Glib or POE in large projects where performance matters.
		1108
		1109	=back
		1110
		1111	=head2 BENCHMARKING SMALL SERVERS
		1112
		1113	While event loops should scale (and select-based ones do not...) even to
		1114	large servers, most programs we (or I :) actually write have only a few
		1115	I/O watchers.
		1116
		1117	In this benchmark, I use the same benchmark program as in the large server
		1118	case, but it uses only eight "servers", of which three are active at any
		1119	one time. This should reflect performance for a small server relatively
		1120	well.
		1121
		1122	The columns are identical to the previous table.
		1123
		1124	=head3 Results
		1125
		1126	name sockets create request
		1127	EV 16 20.00 6.54
		1128	Event 16 81.27 35.86
		1129	Glib 16 32.63 15.48
		1130	Perl 16 24.62 162.37
		1131	POE 16 261.87 276.28 uses POE::Loop::Event
		1132
		1133	=head3 Discussion
		1134
		1135	The benchmark tries to test the performance of a typical small
		1136	server. While knowing how various event loops perform is interesting, keep
		1137	in mind that their overhead in this case is usually not as important, due
		1138	to the small absolute number of watchers.
		1139
		1140	EV is again fastest.
		1141
		1142	The C-based event loops Event and Glib come in second this time, as the
		1143	overhead of running an iteration is much smaller in C than in Perl (little
		1144	code to execute in the inner loop, and perl's function calling overhead is
		1145	high, and updating all the data structures is costly).
		1146
		1147	The pure perl event loop is much slower, but still competitive.
		1148
		1149	POE also performs much better in this case, but is is stillf ar behind the
		1150	others.
		1151
		1152	=head3 Summary
		1153
		1154	=over 4
		1155
		1156	=item * C-based event loops perform very well with small number of
		1157	watchers, as the management overhead dominates.
		1158
		1159	=back
936		1160
937		1161
938	=head1 FORK	1162	=head1 FORK
939		1163
940	Most event libraries are not fork-safe. The ones who are usually are	1164	Most event libraries are not fork-safe. The ones who are usually are

Diff Legend

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

Comparing AnyEvent/lib/AnyEvent.pm (file contents): Revision 1.64 by root, Fri Apr 25 06:54:08 2008 UTC vs. Revision 1.96 by root, Sat Apr 26 11:16:16 2008 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.64 by root, Fri Apr 25 06:54:08 2008 UTC vs.
Revision 1.96 by root, Sat Apr 26 11:16:16 2008 UTC