Commit eb2c24e
committed
miniscript: add parsing benchmarks
On my system these show (the last two lines are the new ones)
test expression::benches::parse_tree ... bench: 860 ns/iter (+/- 44)
test expression::benches::parse_tree_deep ... bench: 1,481 ns/iter (+/- 66)
test miniscript::benches::parse_segwit0 ... bench: 9,205 ns/iter (+/- 77)
test miniscript::benches::parse_segwit0_deep ... bench: 23,003 ns/iter (+/- 248)
As mentioned in the last commit message, these numbers are 10-20x the
numbers for parsing expressions, meaning that optimizing the expression
parser by itself will not get us a large performance boost.1 parent 17e6cd4 commit eb2c24e
1 file changed
+29
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1449 | 1449 | | |
1450 | 1450 | | |
1451 | 1451 | | |
| 1452 | + | |
| 1453 | + | |
| 1454 | + | |
| 1455 | + | |
| 1456 | + | |
| 1457 | + | |
| 1458 | + | |
| 1459 | + | |
| 1460 | + | |
| 1461 | + | |
| 1462 | + | |
| 1463 | + | |
| 1464 | + | |
| 1465 | + | |
| 1466 | + | |
| 1467 | + | |
| 1468 | + | |
| 1469 | + | |
| 1470 | + | |
| 1471 | + | |
| 1472 | + | |
| 1473 | + | |
| 1474 | + | |
| 1475 | + | |
| 1476 | + | |
| 1477 | + | |
| 1478 | + | |
| 1479 | + | |
| 1480 | + | |
0 commit comments