Thanks for checking. I tried the latest and it is much better. Logs below. First two packets are for 2.0.8-1 and shows 19.8 second interval. Rest are for 2.0.11 and shows around 12 second interval. Similar improvement for 20 second interval. At least it has mostly been fixed.
tcpdump -n -i lo 'port 6343'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on lo, link-type EN10MB (Ethernet), capture size 65535 bytes
2.0.8-1
13:34:25.117597 IP 127.0.0.1.47170 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:34:44.960763 IP 127.0.0.1.47170 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
2.0.11
13:38:45.482381 IP 127.0.0.1.52343 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:38:57.476985 IP 127.0.0.1.52343 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:39:09.471478 IP 127.0.0.1.52343 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:39:21.466185 IP 127.0.0.1.52343 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
Using 20 second interval:
2.0.8-1 (~39.8 seconds)
13:44:22.590410 IP 127.0.0.1.42988 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:45:02.273512 IP 127.0.0.1.42988 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:45:41.956961 IP 127.0.0.1.42988 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
2.0.11 (~24 seconds)
13:46:45.470938 IP 127.0.0.1.47797 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:47:09.458107 IP 127.0.0.1.47797 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:47:33.445218 IP 127.0.0.1.47797 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692