perf: EXC-1793: Add criterion load benchmark #2587
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
berestovskyy
changed the title
berestovskyy
force-pushed
the
andriy/exc-1793-load-bench
branch
2 times, most recently
from
8c00ef1
to
ab78fe7
Compare
berestovskyy
force-pushed
the
andriy/exc-1793-load-bench
branch
from
947cad3
to
77ff778
Compare
basvandijk
approved these changes
Nov 13, 2024
dsarlis
approved these changes
Nov 13, 2024
berestovskyy
force-pushed
the
andriy/exc-1793-load-bench
branch
from
fae7533
to
aca0d68
Compare
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The benchmark installs the specified number of
load_simulatorcanisters using thecanister_creatorand executes the specified amount of rounds. It measures the total time taken to complete the rounds and the throughput, i.e., the number of rounds executed per second (essentially, the FR).By default, each
load_simulatorcanister runs a periodic timer with a one-second interval and accesses stable memory every fifth call.This benchmark is useful for debugging and benchmarking scheduler and sandbox eviction changes. For more realistic testnet load tests, refer to the
dfinity/subnet-load-testerproject.