Skip to content

Commit b78a9b5

Browse files
committed
fix(protocol): clarify per-canister instruction limit and mark performance staging file migrated
Adds "per canister" to the 2B per-round DTS limit in execution.md to distinguish it from the 8B/s subnet-level throughput figure on performance.md. Removes the out-of-scope performance staging file now that its content has been migrated.
1 parent cdac155 commit b78a9b5

2 files changed

Lines changed: 1 addition & 106 deletions

File tree

.migration/learn-hub/out-of-scope/what-is-icp/performance.md

Lines changed: 0 additions & 105 deletions
This file was deleted.

docs/concepts/protocol/execution.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ The execution layer is designed to execute multiple canisters concurrently on di
2727

2828
## Deterministic time slicing
2929

30-
Each execution round is synchronized with block production, which happens roughly once per second. The current per-round instruction limit is approximately 2 billion instructions given present node hardware.
30+
Each execution round is synchronized with block production, which happens roughly once per second. The current per-round instruction limit is approximately 2 billion instructions per canister given present node hardware.
3131

3232
For longer computations (up to 20 billion instructions, or up to 200 billion for code installation), ICP uses **Deterministic Time Slicing (DTS)**. DTS pauses a long-running computation at the end of a round and resumes it in the next, allowing a task to span multiple rounds without slowing block creation. DTS is automatic and transparent to canisters: no special canister code is needed.
3333

0 commit comments

Comments
 (0)