… | |
… | |
210 | Similar to C<async>, but uses a coroutine pool, so you should not call |
210 | Similar to C<async>, but uses a coroutine pool, so you should not call |
211 | terminate or join (although you are allowed to), and you get a coroutine |
211 | terminate or join (although you are allowed to), and you get a coroutine |
212 | that might have executed other code already (which can be good or bad :). |
212 | that might have executed other code already (which can be good or bad :). |
213 | |
213 | |
214 | Also, the block is executed in an C<eval> context and a warning will be |
214 | Also, the block is executed in an C<eval> context and a warning will be |
215 | issued in case of an exception instead of terminating the program, as C<async> does. |
215 | issued in case of an exception instead of terminating the program, as |
|
|
216 | C<async> does. As the coroutine is being reused, stuff like C<on_destroy> |
|
|
217 | will not work in the expected way, unless you call terminate or cancel, |
|
|
218 | which somehow defeats the purpose of pooling. |
216 | |
219 | |
217 | The priority will be reset to C<0> after each job, otherwise the coroutine |
220 | The priority will be reset to C<0> after each job, otherwise the coroutine |
218 | will be re-used "as-is". |
221 | will be re-used "as-is". |
219 | |
222 | |
220 | The pool size is limited to 8 idle coroutines (this can be adjusted by |
223 | The pool size is limited to 8 idle coroutines (this can be adjusted by |
… | |
… | |
242 | last if @pool >= $POOL_SIZE; |
245 | last if @pool >= $POOL_SIZE; |
243 | push @pool, $current; |
246 | push @pool, $current; |
244 | |
247 | |
245 | $current->prio (0); |
248 | $current->prio (0); |
246 | schedule; |
249 | schedule; |
247 | } |
250 | } |
248 | } |
251 | } |
249 | |
252 | |
250 | sub async_pool(&@) { |
253 | sub async_pool(&@) { |
251 | # this is also inlined into the unlock_scheduler |
254 | # this is also inlined into the unlock_scheduler |
252 | my $coro = (pop @pool or new Coro \&pool_handler); |
255 | my $coro = (pop @pool or new Coro \&pool_handler); |
253 | |
256 | |
… | |
… | |
287 | |
290 | |
288 | "Cede" to other coroutines. This function puts the current coroutine into the |
291 | "Cede" to other coroutines. This function puts the current coroutine into the |
289 | ready queue and calls C<schedule>, which has the effect of giving up the |
292 | ready queue and calls C<schedule>, which has the effect of giving up the |
290 | current "timeslice" to other coroutines of the same or higher priority. |
293 | current "timeslice" to other coroutines of the same or higher priority. |
291 | |
294 | |
|
|
295 | Returns true if at least one coroutine switch has happened. |
|
|
296 | |
292 | =item Coro::cede_notself |
297 | =item Coro::cede_notself |
293 | |
298 | |
294 | Works like cede, but is not exported by default and will cede to any |
299 | Works like cede, but is not exported by default and will cede to any |
295 | coroutine, regardless of priority, once. |
300 | coroutine, regardless of priority, once. |
|
|
301 | |
|
|
302 | Returns true if at least one coroutine switch has happened. |
296 | |
303 | |
297 | =item terminate [arg...] |
304 | =item terminate [arg...] |
298 | |
305 | |
299 | Terminates the current coroutine with the given status values (see L<cancel>). |
306 | Terminates the current coroutine with the given status values (see L<cancel>). |
300 | |
307 | |