Meter wasm memory usage #2187
Merged
Meter wasm memory usage #2187
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
jsdt
reviewed
Jan 28, 2025
coolreader18
force-pushed
the
noa/wasm-memory-usage
branch
from
56f8ddd to
69946f8
Compare
coolreader18
force-pushed
the
noa/wasm-memory-usage
branch
from
69946f8 to
8af8e26
Compare
jsdt
approved these changes
Jan 28, 2025
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.
Description of Changes
Add a
record_reducer_allocated_memorymethod toEnergyMonitor, and call it after every reducer run. TheEnergyMonitorimplementation can decide how much it wants to debounce the event.Expected complexity level and risk
1
Testing
This just adds a new hook, but there's not yet an implementation of that hook to test.