synchronous or asynchronus, that is the question

mraful has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: synchronous or asynchronus, that is the question by pc88mxer (Vicar) on Aug 05, 2008 at 21:47 UTC
Here's a simple way to tell... presumably you are sequentially querying some number of devices through SNMP and you are wondering if parallelizing the task would result in a speedup. Just divide up the list of devices into N groups and run N copies of your program (one for each group) at the same time to see if it has any effect on the total running time. Another metric you can look at is the wall-clock time versus the cpu-time of your program. If there is a large discrepancy, presumably it is due to waiting for replies from the devices you are querying.	[reply]
Re: synchronous or asynchronus, that is the question by rob_au (Abbot) on Aug 05, 2008 at 22:41 UTC
The other thing that you should consider when seeking to improve timing on SNMP interactions is the manner of data that you are polling: Are you unnecessarily iterating through SNMP tables or unwanted OIDs? Does the device that you are monitoring supply the requisite information in separate, discrete OIDs? Does the device that you are polling support SNMPv2 and in turn, GET-BULK, which is far more efficient for large set retrieval? (See RFC 1187 for details) These are questions that perhaps might be worth considering before making changes to your processes. `perl -le "print unpack'N', pack'B32', '00000000000000000000001000000000'"`	[reply]
Re: synchronous or asynchronus, that is the question by spivey49 (Monk) on Aug 05, 2008 at 21:34 UTC
My opinion would be an ambiguous "that depends..". If you have a number of operations going on aside from the SNMP operations that do not depend on the SNMP operations I would imagine asynchronicity might give you some performance improvements, assuming of course you have available resources. Of course there are things to consider before going down this road, the scope of variables, file handles, etc come to mind. The Async or Proc::Fork documentation might give you an idea of what problems you may encounter. It might help to be a little more specific about what you are doing now and what you would like to accomplish	[reply]