Tags: dfinity/ic
Tags
feat(Core): Switch to deterministic memory tracker (#10789) This PR unifies page instruction charging. The deterministic memory tracker (DMT) now charges for all combinations of {heap, stable} x {read, write} page access types. The cost is uniform and increased to 5000 instructions per OS page (4KiB). Unchanged is the additional cost of copying dirty pages after the message execution (3000 instructions per page). So overall, the costs change like this: ``` previously dmt heap read: 0 5000 heap write: *1000 *5000 stable read: 0 5000 stable write: *1000 *5000 ``` * additionally charged for copy overhead after the message (+3000) The dirty stable pages tracking via the injected system API replacements is changed: The instruction counter is no longer decreased, because the DMT does it automatically. But the bitmap tracking of stable pages is kept, because it's still needed to limit overall stable memory access. As a consequence of this change, heap accesses are charged deterministically and immediately (during the message/slice, rather than afterwards), which means that messages with lots of heap accesses are DTS'd properly. While this incurs additional cycle costs, it will allow us to increase the Wasm heap size to much more than the current 6GiB limit. Squashed from #10536 --------- Co-authored-by: Michael Weigelt <michael.weigelt@dfinity.org> Co-authored-by: michael-weigelt <122277901+michael-weigelt@users.noreply.github.com>
This PR unifies page instruction charging. The deterministic memory t…
…racker (DMT) now charges for all combinations of {heap, stable} x {read, write} page access types. The cost is uniform and increased to 5000 instructions per OS page (4KiB).
Unchanged is the additional cost of copying dirty pages after the message execution (3000 instructions per page).
So overall, the costs change like this:
```
previously dmt
heap read: 0 5000
heap write: *1000 *5000
stable read: 0 5000
stable write: *1000 *5000
*additionally charged for copy overhead after the message (+3000)
```
The dirty stable pages tracking via the injected system API replacements is changed: The instruction counter is no longer decreased, because the DMT does it automatically. But the bitmap tracking of stable pages is kept, because it's still needed to limit overall stable memory access.
As a consequence of this change, heap accesses are charged deterministically and immediately (during the message/slice, rather than afterwards), which means that messages with lots of heap accesses are DTS'd properly. While this incurs additional cycle costs, it will allow us to increase the Wasm heap size to much more than the current 6GiB limit.
chore: Update Mainnet IC revisions canisters file (#10801) Update mainnet system canisters revisions file to include the latest WASM version released on the mainnet. This PR is created automatically using [`mainnet_revisions.py`](https://github.com/dfinity/ic/blob/master/ci/src/mainnet_revisions/mainnet_revisions.py) Co-authored-by: CI Automation <infra+github-automation@dfinity.org>
feat: introduce ErrorCode::CanisterStatusAccessDenied (#10673) This PR introduces a new `ErrorCode::CanisterStatusAccessDenied` to be used by a follow-up PR introducing `snapshot_visibility` field in canister setting to configure who can access the `canister_status` endpoint of the mgmt canister. Introducing the error code must be done in a separate PR rolled-out before actually producing the error code in reject responses so that downgrades are possible and do not fail because the old replica code could not handle the newly introduced and produced error code.
PreviousNext