Discover and read the best of Twitter Threads about #gopacket
Most recents (1)
A few months ago, as users started throwing more API traffic at the Akita client, we started seeing multi-GB memory spikes. 🙀
At first, we hoped for an easy solution. There was none.
This is the story of @markgritter's 25-day journey taming memory usage in a #golang client. 1/
At first, we hoped for an easy solution. There was none.
This is the story of @markgritter's 25-day journey taming memory usage in a #golang client. 1/
@markgritter The first thing @markgritter did, as you would do in most languages, was to profile the system for obvious bottlenecks.
There was one, in the #gopacket reassembly buffer. Memory was persisting even though it wasn't getting used.
Mark fixed this, but the problem persisted. 2/
There was one, in the #gopacket reassembly buffer. Memory was persisting even though it wasn't getting used.
Mark fixed this, but the problem persisted. 2/
@markgritter At this point, the team and I weighed possible next steps.
Since #golang is memory-managed (2x memory overhead no matter what 🙀) and does not expose much control over the garbage collector, we were worried that it was not possible to be able to get memory usage low enough. 3/
Since #golang is memory-managed (2x memory overhead no matter what 🙀) and does not expose much control over the garbage collector, we were worried that it was not possible to be able to get memory usage low enough. 3/
