I don’t think that either NxSDK or NengoLoihi are re-sending data each time you call
run, but you’re right that the size of the probed output will keep increasing, because it’s stored across
In https://github.com/nengo/nengo-loihi/pull/303 we implement
clear_probes for NengoLoihi, but it’s still in development so you’ll have to use that branch (it’s tested, though, so it should work well). That’s what you’ll need to use to clear probed data.
It doesn’t cause it to be reloaded, but there is some processing that NxSDK does each time the simulation is started or stopped. (They’re all listed in that output you posted, things like transferring spikes to the chip, and processing the probe “timeseries” data that comes off the chip. I’m not sure what all exactly is contained in “Configuring registers”, or why it needs to be done each run call.)
If you’re able to use fewer run calls, you’ll get better performance.