Add canton-stress to the tool catalogue - #155
Open
fronow wants to merge 1 commit into
Open
Conversation
An open-source load, performance and cost testing harness for Canton applications. It drives declarative workloads at an application's own DARs through the JSON Ledger API and reports throughput, contention attributed to the contract that lost each race, and traffic cost per transaction. Built against Daml SDK 3.4.11.
This file contains hidden or 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
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.
Adds canton-stress, an open-source (Apache-2.0) load, performance and cost testing harness for Canton applications.
It drives declarative workloads at an application's own DARs through the JSON Ledger API, and reports throughput, contention attributed to the specific contract that lost each race, and traffic cost per transaction. For registries implementing the Token Standard it needs no configuration — the registry is read out of the DAR — and for anything else it generates a starting workload.
Built against Daml SDK 3.4.11, with 166 automated tests and benchmarks against third-party code committed alongside the raw reports.
Checklist