| … | |
… | |
| 603 | Likewise, by setting a higher I<timeout collect interval> you allow libev |
603 | Likewise, by setting a higher I<timeout collect interval> you allow libev |
| 604 | to spend more time collecting timeouts, at the expense of increased |
604 | to spend more time collecting timeouts, at the expense of increased |
| 605 | latency (the watcher callback will be called later). C<ev_io> watchers |
605 | latency (the watcher callback will be called later). C<ev_io> watchers |
| 606 | will not be affected. |
606 | will not be affected. |
| 607 | |
607 | |
| 608 | Many programs can usually benefit by setting the io collect interval to |
608 | Many (busy) programs can usually benefit by setting the io collect |
| 609 | a value near C<0.1> or so, which is often enough for interactive servers |
609 | interval to a value near C<0.1> or so, which is often enough for |
| 610 | (of course not for games), likewise for timeouts. It usually doesn't make |
610 | interactive servers (of course not for games), likewise for timeouts. It |
| 611 | much sense to set it to a lower value than C<0.01>, as this approsaches |
611 | usually doesn't make much sense to set it to a lower value than C<0.01>, |
| 612 | the timing granularity of most systems. |
612 | as this approsaches the timing granularity of most systems. |
| 613 | |
613 | |
| 614 | =back |
614 | =back |
| 615 | |
615 | |
| 616 | |
616 | |
| 617 | =head1 ANATOMY OF A WATCHER |
617 | =head1 ANATOMY OF A WATCHER |
