forked from near/nearcore
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
In this commit, I add a benchmark which sends 150 blocks, where each block contains 100 deploy code transaction. The benchmark is implemented in two ways: * on top of parameter estimator testbed * on top of runtime tested In the first case, I observe a very stage behavior, where at some point block processsing times severely degrades. To reproduce, checkout this commit and run ```console $ cargo test --release --package runtime-params-estimator --lib --features required -- v2::fast --exact --nocapture $ cargo test --release --package runtime-params-estimator --lib --features required -- v2::slow --exact --nocapture ``` Look for `Runtime::apply` lines in the output, they they tell you how long it takes to process one apply. In the `fast` case, every apply takes about 16ms for me. In the `slow` case, apply start at about 30ms, but then abruptly go to 600ms
- Loading branch information
Showing
3 changed files
with
88 additions
and
15 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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