github-actions[bot]
commented
9 months ago Note The flamegraph link only works after you merge. Unchanged benchmarks are omitted.
Collection libraries
Measure different collection libraries written in both Motoko and Rust.
The library names with _rs suffix are written in Rust; the rest are written in Motoko.
The _stable and _stable_rs suffix represents that the library directly writes the state to stable memory using Region in Motoko and ic-stable-stuctures in Rust.
We use the same random number generator with fixed seed to ensure that all collections contain the same elements, and the queries are exactly the same. Below we explain the measurements of each column in the table:
- generate 1m. Insert 1m Nat64 integers into the collection. For Motoko collections, it usually triggers the GC; the rest of the column are not likely to trigger GC.
- max mem. For Motoko, it reports
rts_max_heap_sizeaftergeneratecall; For Rust, it reports the Wasm's memory page * 32Kb. - batch_get 50. Find 50 elements from the collection.
- batch_put 50. Insert 50 elements to the collection.
- batch_remove 50. Remove 50 elements from the collection.
- upgrade. Upgrade the canister with the same Wasm module. For non-stable benchmarks, the map state is persisted by serializing and deserializing states into stable memory. For stable benchmarks, the upgrade takes no cycles, as the state is already in the stable memory.
💎 Takeaways
- The platform only charges for instruction count. Data structures which make use of caching and locality have no impact on the cost.
- We have a limit on the maximal cycles per round. This means asymptotic behavior doesn't matter much. We care more about the performance up to a fixed N. In the extreme cases, you may see an $O(10000 n\log n)$ algorithm hitting the limit, while an $O(n^2)$ algorithm runs just fine.
- Amortized algorithms/GC may need to be more eager to avoid hitting the cycle limit on a particular round.
- Rust costs more cycles to process complicated Candid data, but it is more efficient in performing core computations.
Note
- The Candid interface of the benchmark is minimal, therefore the serialization cost is negligible in this measurement.
- Due to the instrumentation overhead and cycle limit, we cannot profile computations with very large collections.
- The
upgradecolumn uses Candid for serializing stable data. In Rust, you may get better cycle cost by using a different serialization format. Another slowdown in Rust is thatic-stable-structurestends to be slower than the region memory in Motoko.- Different library has different ways for persisting data during upgrades, there are mainly three categories:
- Use stable variable directly in Motoko:
zhenya_hashmap,btree,vector- Expose and serialize external state (
share/unsharein Motoko,candid::Encodein Rust):rbtree,heap,btreemap_rs,hashmap_rs,heap_rs,vector_rs- Use pre/post-upgrade hooks to convert data into an array:
hashmap,splay,triemap,buffer,imrc_hashmap_rs- The stable benchmarks are much more expensive than their non-stable counterpart, because the stable memory API is much more expensive. The benefit is that they get fast upgrade. The upgrade still needs to parse the metadata when initializing the upgraded Wasm module.
hashmapuses amortized data structure. When the initial capacity is reached, it has to copy the whole array, thus the cost ofbatch_put 50is much higher than other data structures.btreecomes from mops.one/stableheapbtreemap.zhenya_hashmapcomes from mops.one/map.vectorcomes from mops.one/vector. Compare withbuffer,puthas better worst case time and space complexity ($O(\sqrt{n})$ vs $O(n)$);gethas a slightly larger constant overhead.hashmap_rsuses thefxhashcrate, which is the same asstd::collections::HashMap, but with a deterministic hasher. This ensures reproducible result.imrc_hashmap_rsuses theim-rccrate, which is the immutable version hashmap in Rust.
Map
| binary_size | generate 1m | max mem | batch_get 50 | batch_put 50 | batch_remove 50 | upgrade | |
|---|---|---|---|---|---|---|---|
| hashmap | 188_910 | 8_370_838_990 | 61_987_852 | 344_911 | 6_593_215_386 | 371_223 | 11_026_881_645 |
| triemap | 194_820 | 13_855_040_241 | 74_216_172 | 254_589 | 661_468 | 650_780 | 15_817_667_776 |
| rbtree | 185_823 | 7_127_314_751 | 57_996_060 | 114_300 | 318_392 | 328_237 | 7_169_324_321 |
| splay | 189_838 | 13_247_301_683 | 53_995_996 | 628_581 | 661_619 | 921_933 | 4_567_871_409 |
| btree | 229_184 | 10_266_012_845 | 31_104_012 | 353_622 | 482_125 | 533_935 | 3_134_166_577 |
| zhenya_hashmap | 188_597 | 2_570_553_414 | 22_773_100 | 60_196 | 70_137 | 82_453 | 3_305_570_068 |
| btreemap_rs | 471_597 | 1_797_168_136 | 27_525_120 | 75_572 | 125_436 | 86_322 | 2_941_064_929 |
| imrc_hashmap_rs | 477_125 | 2_584_652_896 | 244_973_568 | 38_416 | 179_265 | 115_565 | 5_796_576_120 |
| hashmap_rs | 464_990 | 433_765_792 | 73_072_640 | 21_855 | 26_957 | 25_222 | 1_293_478_901 |
Priority queue
| binary_size | heapify 1m | max mem | pop_min 50 | put 50 | pop_min 50 | upgrade | |
|---|---|---|---|---|---|---|---|
| heap | 166_808 | 5_697_879_935 | 29_995_956 | 621_338 | 228_674 | 592_198 | 3_309_814_038 |
| heap_rs | 459_314 | 138_669_874 | 18_219_008 | 57_563 | 23_345 | 57_695 | 511_961_183 |
Growable array
| binary_size | generate 5k | max mem | batch_get 500 | batch_put 500 | batch_remove 500 | upgrade | |
|---|---|---|---|---|---|---|---|
| buffer | 173_215 | 2_570_947 | 65_644 | 95_490 | 800_452 | 170_490 | 3_061_307 |
| vector | 171_563 | 1_920_997 | 24_580 | 126_114 | 183_385 | 175_981 | 4_695_522 |
| vec_rs | 453_413 | 289_090 | 1_310_720 | 17_298 | 30_623 | 25_758 | 3_171_665 |
Stable structures
| binary_size | generate 50k | max mem | batch_get 50 | batch_put 50 | batch_remove 50 | upgrade | |
|---|---|---|---|---|---|---|---|
| btreemap_rs | 471_597 | 76_392_040 | 2_490_368 | 65_130 | 97_326 | 85_331 | 126_467_332 |
| btreemap_stable_rs | 483_530 | 5_255_631_698 | 2_031_616 | 3_167_240 | 5_784_534 | 9_888_430 | 731_136 |
| heap_rs | 459_314 | 7_001_770 | 2_228_224 | 50_072 | 23_593 | 50_044 | 26_819_689 |
| heap_stable_rs | 444_563 | 319_633_532 | 458_752 | 2_674_735 | 278_363 | 2_654_537 | 731_285 |
| vec_rs | 453_413 | 3_079_434 | 2_228_224 | 17_298 | 18_473 | 17_999 | 24_772_181 |
| vec_stable_rs | 441_204 | 75_145_327 | 458_752 | 71_671 | 91_519 | 94_915 | 731_270 |
Environment
- dfx 0.15.2-beta.1
- Motoko compiler 0.10.2 (source vy3jgjpa-6ywclfhp-r10kgfpz-gkw93wh8)
- rustc 1.73.0 (cc66ad468 2023-10-03)
- ic-repl 0.6.0
- ic-wasm 0.7.0
Cryptographic libraries
Measure different cryptographic libraries written in both Motoko and Rust.
- SHA-2 benchmarks
SHA-256/SHA-512. Compute the hash of a 1M Wasm binary.account_id. Compute the ledger account id from principal, based on SHA-224.neuron_id. Compute the NNS neuron id from principal, based on SHA-256.
- Certified map. Merkle Tree for storing key-value pairs and generate witness according to the IC Interface Specification.
generate 10k. Insert 10k 7-character word as both key and value into the certified map.max mem. For Motoko, it reportsrts_max_heap_sizeaftergeneratecall; For Rust, it reports the Wasm's memory page * 32Kb.inc. Increment a counter and insert the counter value into the map.witness. Generate the root hash and a witness for the counter.upgrade. Upgrade the canister with the same Wasm. In Motoko, we use stable variable. In Rust, we convert the tree to a vector before serialization.
SHA-2
| binary_size | SHA-256 | SHA-512 | account_id | neuron_id | |
|---|---|---|---|---|---|
| Motoko | 195_805 | 273_037_084 | 259_835_224 | 34_373 | 24_897 |
| Rust | 476_042 | 82_788_038 | 56_793_082 | 48_636 | 51_163 |
Certified map
| binary_size | generate 10k | max mem | inc | witness | upgrade | |
|---|---|---|---|---|---|---|
| Motoko | 244_500 | 4_763_348_103 | 3_430_044 | 565_117 | 402_073 | 274_275_937 |
| Rust | 498_197 | 6_309_529_789 | 2_228_224 | 1_004_188 | 301_339 | 5_926_705_684 |
Environment
- dfx 0.15.2-beta.1
- Motoko compiler 0.10.2 (source vy3jgjpa-6ywclfhp-r10kgfpz-gkw93wh8)
- rustc 1.73.0 (cc66ad468 2023-10-03)
- ic-repl 0.6.0
- ic-wasm 0.7.0
Sample Dapps
Measure the performance of some typical dapps:
- Basic DAO,
with
heartbeatdisabled to make profiling easier. We have a separate benchmark to measure heartbeat performance. - DIP721 NFT
Note
- The cost difference is mainly due to the Candid serialization cost.
- Motoko statically compiles/specializes the serialization code for each method, whereas in Rust, we use
serdeto dynamically deserialize data based on data on the wire.- We could improve the performance on the Rust side by using parser combinators. But it is a challenge to maintain the ergonomics provided by
serde.- For real-world applications, we tend to send small data for each endpoint, which makes the Candid overhead in Rust tolerable.
Basic DAO
| binary_size | init | transfer_token | submit_proposal | vote_proposal | upgrade | |
|---|---|---|---|---|---|---|
| Motoko | 274_773 | 510_733 | 22_316 | 18_548 | 19_597 | 157_638 |
| Rust | 778_222 | 611_282 | 101_374 | 125_148 | 137_434 | 1_816_495 |
DIP721 NFT
| binary_size | init | mint_token | transfer_token | upgrade | |
|---|---|---|---|---|---|
| Motoko | 221_922 | 481_158 | 29_810 | 8_776 | 89_459 |
| Rust | 790_671 | 239_293 | 368_586 | 89_013 | 2_001_978 |
Environment
- dfx 0.15.2-beta.1
- Motoko compiler 0.10.2 (source vy3jgjpa-6ywclfhp-r10kgfpz-gkw93wh8)
- rustc 1.73.0 (cc66ad468 2023-10-03)
- ic-repl 0.6.0
- ic-wasm 0.7.0
Heartbeat / Timer
Measure the cost of empty heartbeat and timer job.
setTimermeasures both thesetTimer(0)method and the execution of empty job.- It is not easy to reliably capture the above events in one flamegraph, as the implementation detail
of the replica can affect how we measure this. Typically, a correct flamegraph contains both
setTimerandcanister_global_timerfunction. If it's not there, we may need to adjust the script.
Heartbeat
| binary_size | heartbeat | |
|---|---|---|
| Motoko | 137_205 | 23_182 |
| Rust | 23_873 | 1_172 |
Timer
| binary_size | setTimer | cancelTimer | |
|---|---|---|---|
| Motoko | 145_582 | 51_467 | 4_610 |
| Rust | 420_710 | 68_153 | 11_161 |
Environment
- dfx 0.15.2-beta.1
- Motoko compiler 0.10.2 (source vy3jgjpa-6ywclfhp-r10kgfpz-gkw93wh8)
- rustc 1.73.0 (cc66ad468 2023-10-03)
- ic-repl 0.6.0
- ic-wasm 0.7.0
Motoko Specific Benchmarks
Measure various features only available in Motoko.
-
Garbage Collection. Measure Motoko garbage collection cost using the Triemap benchmark. The max mem column reports
rts_max_heap_sizeaftergeneratecall. The cycle cost numbers reported here are garbage collection cost only. Some flamegraphs are truncated due to the 2M log size limit. Thedfx/ic-wasmoptimizer is disabled for the garbage collection test cases due to how the optimizer affects function names, making profiling trickier.- default. Compile with the default GC option. With the current GC scheduler,
generatewill trigger the copying GC. The rest of the methods will not trigger GC. - copying. Compile with
--force-gc --copying-gc. - compacting. Compile with
--force-gc --compacting-gc. - generational. Compile with
--force-gc --generational-gc. - incremental. Compile with
--force-gc --incremental-gc.
- default. Compile with the default GC option. With the current GC scheduler,
-
Actor class. Measure the cost of spawning actor class, using the Actor classes example.
Garbage Collection
| generate 700k | max mem | batch_get 50 | batch_put 50 | batch_remove 50 | |
|---|---|---|---|---|---|
| default | 1_171_395_786 | 51_991_392 | 119 | 119 | 119 |
| copying | 1_171_395_668 | 51_991_392 | 1_171_104_136 | 1_171_195_696 | 1_171_106_949 |
| compacting | 1_672_114_659 | 51_991_392 | 1_290_052_154 | 1_533_417_828 | 1_564_512_242 |
| generational | 2_529_073_372 | 51_999_856 | 999_515_201 | 1_232_740 | 1_103_853 |
| incremental | 29_503_138 | 985_890_580 | 333_755_986 | 336_886_802 | 336_875_628 |
Actor class
| binary size | put new bucket | put existing bucket | get | |
|---|---|---|---|---|
| Map | 299_052 | 813_512 | 16_099 | 16_644 |
Environment
- dfx 0.15.2-beta.1
- Motoko compiler 0.10.2 (source vy3jgjpa-6ywclfhp-r10kgfpz-gkw93wh8)
- rustc 1.73.0 (cc66ad468 2023-10-03)
- ic-repl 0.6.0
- ic-wasm 0.7.0
Publisher & Subscriber
Measure the cost of inter-canister calls from the Publisher & Subscriber example.
| pub_binary_size | sub_binary_size | subscribe_caller | subscribe_callee | publish_caller | publish_callee | |
|---|---|---|---|---|---|---|
| Motoko | 161_257 | 145_541 | 28_593 | 11_963 | 22_864 | 6_430 |
| Rust | 456_613 | 507_753 | 69_189 | 42_865 | 92_768 | 52_116 |
Environment
- dfx 0.15.2-beta.1
- Motoko compiler 0.10.2 (source vy3jgjpa-6ywclfhp-r10kgfpz-gkw93wh8)
- rustc 1.73.0 (cc66ad468 2023-10-03)
- ic-repl 0.6.0
- ic-wasm 0.7.0
Map
Priority queue
Growable array
Stable structures
Statistics
SHA-2
Certified map
Statistics
Basic DAO
DIP721 NFT
Statistics
Heartbeat
Timer
Statistics
Garbage Collection
Actor class
Statistics
Publisher & Subscriber
Statistics
binary_size: 5.10% [-2.63%, 12.84%]
max_mem: no change
cycles: -0.37% [-0.66%, -0.08%]
Overall Statistics
binary_size: 6.65% [4.15%, 9.16%]
max_mem: -1.02% [-2.10%, 0.07%]
cycles: -2.67% [-3.32%, -2.02%]