Conversation
CodSpeed Performance ReportMerging #487 will not alter performanceComparing 🎉 Hooray!
|
| Benchmark | BASE |
HEAD |
Change | |
|---|---|---|---|---|
| 🆕 | base_convert/128/128/10/be |
N/A | 13.9 ms | N/A |
| 🆕 | base_convert/128/128/10/le |
N/A | 3.5 ms | N/A |
| 🆕 | base_convert/192/192/10/be |
N/A | 22.5 ms | N/A |
| 🆕 | base_convert/192/192/10/le |
N/A | 9.4 ms | N/A |
| 🆕 | base_convert/256/256/10/be |
N/A | 33.6 ms | N/A |
| 🆕 | base_convert/256/256/10/le |
N/A | 18.4 ms | N/A |
| 🆕 | base_convert/384/384/10/be |
N/A | 65 ms | N/A |
| 🆕 | base_convert/384/384/10/le |
N/A | 47.6 ms | N/A |
| 🆕 | base_convert/4096/4096/10/be |
N/A | 132.7 ms | N/A |
| 🆕 | base_convert/4096/4096/10/le |
N/A | 129.6 ms | N/A |
| 🆕 | base_convert/512/512/10/be |
N/A | 110.1 ms | N/A |
| 🆕 | base_convert/512/512/10/le |
N/A | 91.7 ms | N/A |
| 🆕 | base_convert/64/64/10/be |
N/A | 8.3 ms | N/A |
| 🆕 | base_convert/64/64/10/le |
N/A | 615.7 µs | N/A |
| 🆕 | fmt/binary/128 |
N/A | 8.7 ms | N/A |
| 🆕 | fmt/binary/192 |
N/A | 12.5 ms | N/A |
| 🆕 | fmt/binary/256 |
N/A | 17.6 ms | N/A |
| 🆕 | fmt/binary/384 |
N/A | 25.8 ms | N/A |
| 🆕 | fmt/binary/4096 |
N/A | 9.2 ms | N/A |
| 🆕 | fmt/binary/512 |
N/A | 37.2 ms | N/A |
| ... | ... | ... | ... | ... |
ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.
|
They run instantly in codspeed but maybe they're too many? wdyt @Rjected @prestwich |
|
I think that having 180 benches just for base conversion and formatting is probably overkill and likely to create some noise. i'd prefer to cut that down a bit. Conversion is a 1-time cost and can be amortized in program life-cycle, and not the perf focus of the lib. let's have the majority of the benches focus on the math and allocations of using the uints |
|
how about now? |
No description provided.