-
Notifications
You must be signed in to change notification settings - Fork 712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gopacket seems to statically initialise a lot of memory... #466
Comments
Is this a problem? |
Makes debugging the heap usage a little tougher, and seems like a shame On Mon, Sep 14, 2015 at 5:55 PM, Peter Bourgon [email protected]
|
Well, I guess the subtext to that question was "is there anything we can do about it" save forking and cleaning up gopacket? |
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? |
I'm fine with ripping packet capture out of Scope. Failed experiment for the time being. |
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. |
The text was updated successfully, but these errors were encountered: