Feat/perf improv ( 600x ) #9
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Investigation using the "Blocking Profiler" revealed that a lot of time was spent during buffer reading. Using io.copy to read the full HTTP response, and then reading from that in the memory buffer resulted in a great performance boost. The parsing step initially took around ~300ms, now it is in the sub-millisecond range ( ~500µs ).
Initially, I thought passing the resp.Body directly into the html.Tokenizer would reduce memory usage, without causing any performance issues. However, it seems like every time the application tries to read from the HTTP response, it is an expensive operation.