Improving Node-Metrics backend canister #712
Merged
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 is especially relevant when stable memory is empty (before it risked exhausting the number of instructions allowed for timers) 37B before vs 700M now.
This was mainly due to the multiple accesses to stable map using
metrics_before_ts
querying the metrics before a ts for a specificnode_id
. Replaced now withlatest_metrics
which goes through the data only once.The use of unbounded data for
NodeMetricsStored
Added Virtual Memory needed for storing additional data structures (node providers mapping in the future)
Modified
NodeMetricsStored
serialization to be bounded