Raja Subramanian c3964ba2eb Use sync.Pool for objects in packet path. (#4066) ...

* Use sync.Pool for objects in packet path.

Seeing cases of forwarding latency spikes that aling with GC.

This might be a bit overkill, but using sync.Pool for small +
short-lived objects in packet path.

Before this, all these were increasing in alloc_space heap profile
samples over time. With these, there is no increase (actually the lines
corresponding to geting from pool does not even show up in heap
accounting when doing `list` in `pprof`)

* merge

* Paul feedback

2025-11-14 16:13:23 +05:30

..

base.go

Use sync.Pool for objects in packet path. (#4066)

2025-11-14 16:13:23 +05:30

leaky_bucket.go

Update deque and friends. (#3276)

2024-12-20 07:16:14 +05:30

no_queue.go

Update deque and friends. (#3276)

2024-12-20 07:16:14 +05:30

pacer.go

Use sync.Pool for objects in packet path. (#4066)

2025-11-14 16:13:23 +05:30

pass_through.go

Misc/minor clean up. (#3183)

2024-11-17 12:14:46 +05:30

probe_observer.go

Dampen oscillations in loss based congestion detection when using TWCC. (#3256)

2024-12-16 15:26:23 +05:30