Introducing "canbench": a benchmarking framework for canisters

Hey everyone!

I wanted to share with you a little tool that we’ve been working on and just open-sourced. It’s called canbench and it’s a benchmarking framework for canisters.

canbench is a tool that we built organically when we were trying to understand the performance of canisters and libraries that we were building. Once setup, it allows you to effortlessly monitor performance regressions as well as analyze the performance of your code.

Here is an example of what the canbench CI integration looks like (screenshots below):

Performance changes are detected:

No performance changes are detected:

Currently canbench only supports Rust canisters, but support for other languages can easily be introduced. Let us know if this is something you’d like to see. Happy benching :weight_lifting_man:


Hey @ielashi,

this is awesome, and as such, should be added to GitHub - dfinity/awesome-internet-computer: A curated list of awesome projects and resources relating to the Internet Computer Protocol :wink:

Would you mind doing a PR?


Anyone got any ideas of what might be causing this error?

“error parsing result of benchmark test. Result: module”

1 Like

Sure, will do :slight_smile:

It looks like there’s an error when executing the benchmark. Can you share the benchmark code and/or wasm module that’s causing this error?

1 Like

I am getting an error when trying to run canbench

Error executing benchmark create_account_bench. Error:
ingress Completed: Reply: 0x4449444c016c01b3c4b1f204680100010a00000000000000000101
ingress Err: IC0503: Canister rwlgt-iiaaa-aaaaa-aaaaa-cai trapped explicitly: failed to decode call arguments: Custom(Cannot parse header 

Caused by:
    binary parser error: io error)
Err: IC0304: Attempt to execute a message on canister rwlgt-iiaaa-aaaaa-aaaaa-cai which contains no Wasm module

Apologies for the slow response here. Is there code you can point me to to triage the problem? My github username is “ielashi” in case you’d like to share access to your code.

1 Like


1 Like

Hi @ielashi, Do you know why I am getting this error?

1 Like

@zohaib29 Is your canister taking in init args? canbench doesn’t currently support deploying a wasm that has init args. If yes, can you try removing them and see if that fixes the issue?

We should be able to add support for specifying the init args in canbench.yml - it’s not that much work.


Yes, after removing init args it worked. Thanks!

1 Like

Thanks for the feedback. I added two issues to improve canbench in that regard.


Update: The newest version of canbench (version 0.1.4) now supports canisters with init args. See here for the documentation. Big thanks to @frederikrothenberger for adding this feature!

cc @zohaib29