Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: instantiate perf observer for each iteration #3585

Merged
merged 2 commits into from
Jun 13, 2022
Merged

Conversation

MrArnoldPalmer
Copy link
Contributor

Changes to instantiate a PerformanceObserver instance for each
iteration of a benchmark run. This prevents the observer from being
killed before all iterations of the wrapped function run due to
environment changes that may cause the observer from falling out of
scope and being GCed. Previously in github actions only a single run's
results were recorded as the observer was killed after the first
iteration, though this wasn't the case when running locally.

Additionally adds the option to record profiles for benchmarks and write
them to a directory. This can be used to compare call stacks of
benchmarks across changes to the code.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Changes to instantiate a `PerformanceObserver` instance for each
iteration of a benchmark run. This prevents the observer from being
killed before all iterations of the wrapped function run due to
environment changes that may cause the observer from falling out of
scope and being GCed. Previously in github actions only a single run's
results were recorded as the observer was killed after the first
iteration, though this wasn't the case when running locally.

Additionally adds the option to record profiles for benchmarks and write
them to a directory. This can be used to compare call stacks of
benchmarks across changes to the code.
@MrArnoldPalmer MrArnoldPalmer requested a review from a team June 8, 2022 19:42
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Jun 8, 2022
@mergify
Copy link
Contributor

mergify bot commented Jun 13, 2022

Thank you for contributing! ❤️ I will now look into making sure the PR is up-to-date, then proceed to try and merge it!

@mergify mergify bot added the pr/ready-to-merge This PR is ready to be merged. label Jun 13, 2022
@mergify
Copy link
Contributor

mergify bot commented Jun 13, 2022

Merging (with squash)...

@mergify mergify bot merged commit 3827d93 into main Jun 13, 2022
@mergify mergify bot deleted the fix/bench-iterations branch June 13, 2022 14:37
@mergify
Copy link
Contributor

mergify bot commented Jun 13, 2022

Merging (with squash)...

@mergify mergify bot removed the pr/ready-to-merge This PR is ready to be merged. label Jun 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution/core This is a PR that came from AWS.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants