On 21 September 2012 08:23, Giuseppe Modugno <[email protected]> wrote: > Another idea would be the use of caching data helper, but I don't if it > could be a real solution. Consider that many variables accessed from the > serial bus are analog signals (voltages, currents, ...) and they may > change frequently over time, so the cache timeout period could be around > 100-500ms, no more. Usually the user polls the agent every 1-10s with > multiple-variables requests, so the serial bus access won't be avoided.
Using a cache with a very low timeout (say 1s) would probably be the simplest approach here. Processing the first varbind in each query would trigger the cache reload (and hence the serial bus access). Subsequent varbinds within the same request could then use this cached datam thus avoiding the serial delays (as well as reporting consistent values - all retrieved via the same serial bus query). By the time of the next poll, the cache would be stale, so the process would begin again. Dave ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
