Thanks for the reply. Neither approach sounds ideal. They take a lot of work, a lot of disk space, or a lot of SSH calls. Maybe there are some other ways to solve this.
Qou're quite right, unfortunately
It sounds like Cacti does not cache multiple calls to the same script, which I already guessed by looking at the cacti.log file. Would caching (within the same polling cycle) be a reasonable solution? It seems to me it would have some other benefits, such as making sure all data is totally consistent within the polling cycle.
Sure. It's an old request. But no code has been contributed yet
If Cacti cannot do this, I might either a) add it myself or b) hack my scripts so they write their last result into /tmp/[script]_[hostname].txt and check for a cache hit (a file less than 5 minutes old) before actually going to fetch the data. Can you comment on the dangers or benefits of such an approach?
Approach b) is the current workaround. Approach a) would be the better one.