gopacket seems to statically initialise a lot of memory...

[tomwilkie]

[peterbourgon]

Is this a problem?

[tomwilkie]

Makes debugging the heap usage a little tougher, and seems like a shame
considering its not turned on by default.

On Mon, Sep 14, 2015 at 5:55 PM, Peter Bourgon notifications@github.com
wrote:

Is this an actual problem?

—
Reply to this email directly or view it on GitHub
#466 (comment).

[peterbourgon]

Well, I guess the subtext to that question was "is there anything we can do about it" save forking and cleaning up gopacket?

[tomwilkie]

An alternative would be to move the packet inspection code into a separate binary and only launch it when we enable that feature.

I think we probably want to do this for the tracer anyway (as its performance critical), so perhaps the same reasoning applies here?

[peterbourgon]

I'm fine with ripping packet capture out of Scope. Failed experiment for the time being.

[tomwilkie]

I wouldn't go that far just yet; its still a candidate for getting better metrics. Maybe move it to experimental? That will prevent some of the bit rot.