APCng storage - avoid worst-case memory usage in buildPermutationTree #123
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
| @@ -539,10 +530,9 @@ private function getValues(string $type, array $metaData): array /** @phpstan-ig | |||
| if (isset($metaData['buckets'])) { | |||
| $metaData['buckets'][] = 'sum'; | |||
| $labels[] = $metaData['buckets']; | |||
| $metaData['labelNames'][] = '__histogram_buckets'; | |||
There was a problem hiding this comment.
Since I don't use the number of label names anymore, I removed that parameter from buildPermutationTree and removed this line as it seemed unused. I don't see any change in the output for histograms but if this actually used then I can re-add it.
Signed-off-by: Josh Hoffer <[email protected]>
|
This would be great to land, we are hitting the PHP limit as well. |
xocasdashdash
added a commit
to PaddleHQ/prometheus_client_php
that referenced
this pull request
Aug 29, 2024
|
I've tested a copy of this PR and it works well to reduce memory usage with histograms |
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.
The peak memory usage of the APCng storage adapter while collecting the metrics for display is currently always the worst-case for the cardinality of the metric label values.
This change replaces the buildPermutationTree implementation with a (cartesian product) generator which avoids keeping every metric label value permutation in memory at once. This can reduce peak memory usage by orders of magnitude for metrics with high cardinality but sparse actual usage. This helps avoid exceeding the PHP memory_limit.
Besides the reduced memory usage, I haven't seen much of a difference in how long
buildPermutationTreetakes to run. (To improve that, only the actually used metric label pairs could be to tracked separately to avoid building the permutations completely.)