exploration: how many profiles are buffered if the agent endpoint is down? #3524
Conversation
This file contains hidden or 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
…down? Answer: It should be <= 7 profiles. The last profile of the service we were looking at was 1 MiB and the OOM happened after 3 minutes, so this is unlikey to be explained by the buffering of profile data. For details look at the comments in this PR.
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.
Answer: It should be <= 7 profiles. The last profile of the service we were looking at was 1 MiB and the OOM happened after 3 minutes, so this is unlikey to be explained by the buffering of profile data.
For details look at the comments in this PR.