#internet-computer #benchmark #canister #ic #perf

bin+lib canbench

A benchmarking framework for canisters on the Internet Computer

7 releases

new 0.1.7 Oct 2, 2024
0.1.6 Sep 20, 2024
0.1.5 Aug 27, 2024
0.1.4 May 21, 2024
0.1.1 Feb 9, 2024

#257 in Magic Beans

Download history 1406/week @ 2024-06-16 1237/week @ 2024-06-23 1177/week @ 2024-06-30 1171/week @ 2024-07-07 942/week @ 2024-07-14 1538/week @ 2024-07-21 1538/week @ 2024-07-28 2066/week @ 2024-08-04 1668/week @ 2024-08-11 1926/week @ 2024-08-18 1756/week @ 2024-08-25 1873/week @ 2024-09-01 1566/week @ 2024-09-08 1528/week @ 2024-09-15 1600/week @ 2024-09-22 1926/week @ 2024-09-29

6,705 downloads per month

Apache-2.0

50KB
576 lines

Apache-2.0 Chat on the Forum

canbench

canbench is a tool for benchmarking canisters on the Internet Computer.

Background

Canister smart contracts on the Internet Computer consume compute and memory resources. Given that resources are finite, there are bounds in place when canisters execute a message (transaction):

  1. Instructions: a monotonically increasing counter that's corelated with the amount of computation and memory accesses.
  2. Dirty Pages: the number of memory pages that are written to.

A single message execution must stay within the allowed bounds, otherwise it's terminated. canbench provides developers the tools and insights to understand how their code is using instructions and memory. Support for reporting dirty pages will be available once there's a way to retrieve dirty page information from the IC.

Use Cases

  • Understanding how a canister consumes instructions, heap memory, and stable memory.
  • Detecting performance regressions locally or on CI.
  • Analyzing where performance bottlenecks are present.

Features

  • Metrics that are relevant

    Typically benchmarking tools run a benchmark multiple times and return the average time. On the Internet Computer, where instrumentation is deterministic, this approach is neither ideal nor insightful. Instead, canbench reports the number of instructions consumed, as well as changes to both heap and stable memories.

  • Easy detection of regressions

    canbench allows you to persist the benchmarking results in your canister's repository. Storing the benchmarking results allows canbench to determine how the performance has changed relative to the past to detect regressions.

  • Generous instruction limit

    While messages on the Internet Computer are bound to a few billion instructions, canbench can run benchmarks that are up to 10 trillion instructions, giving you the freedom to write resource-intensive benchmarks as needed.

  • Language Agnostic

    canbench can, in theory, benchmark canisters written in any language. Initially support for only Rust exists, but support for additional languages can easily be introduced.

Installation

cargo install canbench

Quickstart (Rust)

See the crate's documentation.

Github CI Support

canbench can be included in Github CI to automatically detect performance changes. Have a look at the workflows in this repository for working examples. You'll need the following:

  1. Scripts for executing the benchmark, which can be found in the scripts directory.
  2. A workflow for canbench to post a comment with the benchmarking results. See canbench-post-comment.yml.
  3. A job for uploading the PR number to the artifacts. This is necessary for step #2 to work correctly. See upload-pr-number in ci.yml.
  4. The benchmarking job in CI. See benchmark-fibonacci-example in ci.yml.

Once you have the CI workflow set up, the job will pass if there are no significant performance changes detected and fail otherwise. A comment is added to the PR to show the results. See this PR for an example.

Dependencies

~20–36MB
~612K SLoC