Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1337 from pmconrad/performance_test
Add performance test
- Loading branch information
Showing
3 changed files
with
201 additions
and
23 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
HOW TO | ||
====== | ||
|
||
This small test suite serves to demonstrate two key points about the performance | ||
of our current implementation. The subject was talked about in detail at | ||
BitFest Amsterdam, Sep 22, 2018. | ||
|
||
The original description of the 100,000 transactions per second test can be | ||
found at https://bitshares.org/blog/2015/06/08/measuring-performance/ . | ||
|
||
Prepare | ||
------- | ||
|
||
1. Follow the build instructions in the top-level README file. | ||
2. Instead of running ``make`` you can run ``make performance_test`` to build | ||
only the test suite. | ||
3. Run ``tests/performance_test -t performance_tests/<testcase>`` | ||
|
||
|
||
100k TX/s | ||
--------- | ||
|
||
``tests/performance_test -t performance_tests/one_hundred_k_benchmark`` | ||
|
||
This test will create 200,000 accounts, make two transfers from each account, | ||
then create an asset and issue tokens to each account, for a total of one | ||
million operations. | ||
|
||
Different operation types have different execution times, but on fairly modern | ||
off-the-shelf hardware an average of 100,000 transactions per second should be | ||
achieved. | ||
|
||
Signature verification | ||
---------------------- | ||
|
||
``tests/performance_test -t performance_tests/sigcheck_benchmark`` | ||
|
||
This suite pre-creates 100,000 signatures and then measures how long it takes | ||
to verify them. Results vary depending on CPU type and clockspeed, but should be | ||
somewhere between 5,000 and 20,000 per second. |
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