Bake in pprof data from production to optimise hot paths #7
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
This data was collected by setting `COLLECT_METRICS=yes` on production and then running: ```bash $ while true; do curl http://localhost:6060/debug/pprof/profile?seconds=30 --output profiles/$(date +%s).pprof; sleep 270; done ``` To gather a chunk of metrics every 5 mins for 30 seconds for a couple of hours. The traffic to the server came in bursts, but included lots of visits to jupyter- which is massively asset heavy and makes loads of calls to /api/v1/auth. At some point we can start thinking about gathering data from loads of instances over many days with lots of requests; at that point this commit will be useful prep
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.
This data was collected by setting
COLLECT_METRICS=yeson production and then running:To gather a chunk of metrics every 5 mins for 30 seconds for a couple of hours. The traffic to the server came in bursts, but included lots of visits to jupyter- which is massively asset heavy and makes loads of calls to /api/v1/auth.
At some point we can start thinking about gathering data from loads of instances over many days with lots of requests; at that point this commit will be useful prep