Guest Profile sample period configuration support#456
Merged
Conversation
This change matches the configuration support for guest profling provided by wasmtime and is useful for integrators making use of guest profiling to be able to get a more fine/coarse grained view of the execution of their services (and also balance data generated, overhead, etc.). In preparing to submit this change for review, I first saw that there is an alternative implementation of this with #437, doing mostly the same things in a slightly different form.
cceckman-at-fastly
previously approved these changes
Mar 18, 2025
Co-authored-by: Charles Eckman <charles.eckman@fastly.com>
cceckman-at-fastly
approved these changes
Mar 18, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 change matches the configuration support for guest profling provided by wasmtime and is useful for integrators making use of guest profiling to be able to get a more fine/coarse grained view of the execution of their services (and also balance data generated, overhead, etc.).
In preparing to submit this change for review, I first saw that there is an alternative implementation of this with
#437, doing mostly the same things in a slightly different form.