>>>>> On Thu, 2 Jun 2005 07:44:14 +0200, Magnus Fromreide <[EMAIL PROTECTED]> >>>>> said:
>> I suspect two things: >> 1) That master agent talking to subagent with simultaneous queries slows >> down the speed? Magnus> That shouldn't be the the case - there is additional overhead Magnus> as you are issuing twice as many requests but it shouldn't be Magnus> that bad and as the times you are quoting are very big I'd say Magnus> you have either a very large number of objects or there are Magnus> some other problem. There are some optimizations (5.2 and beyond... hmm.. might be 5.1 actually, I forget) that help walk (getnext actually) requests find the next spot to start on whenever possible. It's possible two walks would actually bypass the optimization, but knowing how it works it should work until you hit like 8-9 walks at once. However, remember that the agent only processes one request at a time so you would get some compounding as the 2 application timing and the agent timings interplayed. Ideally if the applications themselves required 0ms to achieve there end you would get only a doubling. But with two apps and their own overhead it will affect the results (though the app should be much faster than the agent). -- Wes Hardaker Sparta, Inc. ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
