chore: remove unused brillig function calls#11180
Conversation
f670905 to
f895f82
Compare
Changes to Brillig bytecode sizes
🧾 Summary (10% most significant diffs)
Full diff report 👇
|
Changes to number of Brillig opcodes executed
🧾 Summary (10% most significant diffs)
Full diff report 👇
|
Changes to circuit sizes
🧾 Summary (10% most significant diffs)
Full diff report 👇
|
There was a problem hiding this comment.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'Test Suite Duration'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.
| Benchmark suite | Current: 236ffb6 | Previous: e48a0d8 | Ratio |
|---|---|---|---|
test_report_zkpassport_noir-ecdsa_ |
2 s |
1 s |
2 |
test_report_zkpassport_noir_rsa_ |
2 s |
1 s |
2 |
This comment was automatically generated by workflow using github-action-benchmark.
CC: @TomAFrench
There was a problem hiding this comment.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'Brillig Execution Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.
| Benchmark suite | Current: 385d03c | Previous: 2c2a7b8 | Ratio |
|---|---|---|---|
semaphore-depth-10 |
0.037 s |
0.027 s |
1.37 |
This comment was automatically generated by workflow using github-action-benchmark.
CC: @TomAFrench
There was a problem hiding this comment.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'Compilation Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.
| Benchmark suite | Current: f895f82 | Previous: 2c2a7b8 | Ratio |
|---|---|---|---|
sha512-100-bytes |
1.92 s |
1.596 s |
1.20 |
This comment was automatically generated by workflow using github-action-benchmark.
CC: @TomAFrench
f895f82 to
385d03c
Compare
|
This is removing too much currently. Note that there was another attempt at this a while back in #9659. It was reverted in #9710 as it resulted in failures inside of aztec-packages. It should be fixable but you will need to take care and do thorough testings against aztec-packages (and migrate any reproductions back into this repository). |
There was a problem hiding this comment.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'Execution Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.
| Benchmark suite | Current: 236ffb6 | Previous: e48a0d8 | Ratio |
|---|---|---|---|
sha512-100-bytes |
0.088 s |
0.053 s |
1.66 |
This comment was automatically generated by workflow using github-action-benchmark.
CC: @TomAFrench
Description
Problem
closes #11181
Summary
not tested yet
Additional Context
User Documentation
Check one:
PR Checklist
cargo fmton default settings.