… | |
… | |
40 | This module does not export anything and does not require you to do |
40 | This module does not export anything and does not require you to do |
41 | anything special apart from loading it *before doing any non-blocking |
41 | anything special apart from loading it *before doing any non-blocking |
42 | requests with Net::SNMP*. It is recommended but not required to load |
42 | requests with Net::SNMP*. It is recommended but not required to load |
43 | this module before "Net::SNMP". |
43 | this module before "Net::SNMP". |
44 | |
44 | |
|
|
45 | GLOBAL VARIABLES |
|
|
46 | $AnyEvent::SNMP::MAX_OUTSTANDING (default: 50, dynamic) |
|
|
47 | AnyEvent::SNMP::set_max_outstanding $new_value |
|
|
48 | Use this package variable to restrict the number of outstanding SNMP |
|
|
49 | requests at any point in time. |
|
|
50 | |
|
|
51 | Net::SNMP is very fast at creating and sending SNMP requests, but |
|
|
52 | much slower at parsing (big, bulk) responses. This makes it easy to |
|
|
53 | request a lot of data that can take many seconds to parse. |
|
|
54 | |
|
|
55 | In the best case, this can lead to unnecessary delays (and even |
|
|
56 | time-outs, as the data has been received but not yet processed) and |
|
|
57 | in the worst case, this can lead to packet loss, when the receive |
|
|
58 | queue overflows and the kernel can no longer accept new packets. |
|
|
59 | |
|
|
60 | To avoid this, you can (and should) limit the number of outstanding |
|
|
61 | requests to a number low enough so that parsing time doesn't |
|
|
62 | introduce noticable delays. |
|
|
63 | |
|
|
64 | Unfortunately, this number depends not only on processing speed and |
|
|
65 | load of the machine running Net::SNMP, but also on the network |
|
|
66 | latency and the speed of your SNMP agents. |
|
|
67 | |
|
|
68 | AnyEvent::SNMP tries to dynamically adjust this number dynamically |
|
|
69 | upwards and downwards. |
|
|
70 | |
|
|
71 | Increasing $MAX_OUTSTANDING will not automatically use the "extra |
|
|
72 | request slots. To increase $MAX_OUTSTANDING" and make |
|
|
73 | ""AnyEvent::SNMP" make use of the extra paralellity, call |
|
|
74 | "AnyEvent::SNMP::set_max_outstanding" with the new value, e.g.:" |
|
|
75 | |
|
|
76 | AnyEvent::SNMP::set_max_outstanding 500; |
|
|
77 | |
|
|
78 | Although due to the dynamic adjustment, this might have little |
|
|
79 | lasting effect. |
|
|
80 | |
|
|
81 | Note that you can use Net::SNMP::XS to speed up parsing of responses |
|
|
82 | considerably. |
|
|
83 | |
|
|
84 | $AnyEvent::SNMP::MIN_RECVQUEUE (default: 8) |
|
|
85 | $AnyEvent::SNMP::MAX_RECVQUEUE (default: 64) |
|
|
86 | These values specify the minimum and maximum receive queue length |
|
|
87 | (in units of one response packet). |
|
|
88 | |
|
|
89 | When AnyEvent::SNMP handles $MAX_RECVQUEUE or more packets per |
|
|
90 | iteration it will reduce $MAX_OUTSTANDING. If it handles less than |
|
|
91 | $MIN_RECVQUEUE, it increases $MAX_OUTSTANDING. |
|
|
92 | |
|
|
93 | This has the result of adjusting the number of outstanding requests |
|
|
94 | so that the recv queue is between the minimum and maximu, usually. |
|
|
95 | |
|
|
96 | This algorithm works reasonably well as long as the responses, |
|
|
97 | response latencies and processing times are the same size per packet |
|
|
98 | on average. |
|
|
99 | |
|
|
100 | COMPATIBILITY |
|
|
101 | This module may be used as a drop in replacement for the |
|
|
102 | Net::SNMP::Dispatcher in existing programs. You can still call |
|
|
103 | "snmp_dispatcher" to start the event-loop, but then you loose the |
|
|
104 | benefit of mixing Net::SNMP events with other events. |
|
|
105 | |
|
|
106 | use AnyEvent::SNMP; |
|
|
107 | use Net::SNMP; |
|
|
108 | |
|
|
109 | # just use Net::SNMP as before |
|
|
110 | |
|
|
111 | # ... start non-blocking snmp request(s)... |
|
|
112 | Net::SNMP->session ( |
|
|
113 | -hostname => "127.0.0.1", |
|
|
114 | -community => "public", |
|
|
115 | -nonblocking => 1, |
|
|
116 | )->get_request (-callback => sub { ... }); |
|
|
117 | |
|
|
118 | snmp_dispatcher; |
|
|
119 | |
45 | SEE ALSO |
120 | SEE ALSO |
46 | AnyEvent, Net::SNMP, Net::SNMP::EV. |
121 | AnyEvent, Net::SNMP, Net::SNMP::XS, Net::SNMP::EV. |
47 | |
122 | |
48 | AUTHOR |
123 | AUTHOR |
49 | Marc Lehmann <schmorp@schmorp.de> |
124 | Marc Lehmann <schmorp@schmorp.de> |
50 | http://home.schmorp.de/ |
125 | http://home.schmorp.de/ |
51 | |
126 | |
|
|
127 | POD ERRORS |
|
|
128 | Hey! The above document had some coding errors, which are explained |
|
|
129 | below: |
|
|
130 | |
|
|
131 | Around line 79: |
|
|
132 | Unterminated C<...> sequence |
|
|
133 | |