feat: Only keep HTTP headers we want to keep #254
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
When processing HTTP request/response pairs, the header structs contain a lot of information we do not care about. From profiling data, we can see a large portion of the agent's live bytes are coming from
textproto.readMimeHeader()
, where headers are created. These bytes are held until the request/response pair is processed.This PR adds extracts a copy of the header entries we care about and replaces the Header struct on the request/response, meaning the previous larger Header struct can be GC'd earlier and not wait for pairing to complete.
Short description of the changes
How to verify that this has the expected result
The header that's part of the HTTP request / response now only contains entries we care about and allows the expensive original Header to be cleaned up earlier.