Releases: ordo-one/package-benchmark
1.22.1
Contributors
Assets 2
1.22.0
1.22.0 (2024-01-11)
For benchmarks that are not completely stable (in e.g. syscall/malloc count) due to use of e.g. async or networking, it is desirable to also be able to specify some leeway for benchmarks even for the absolute checks from thresholds.
This fixes #220
By default the behaviour for absolute thresholds checks are as previously (strict, zero improvements/regressions are allowed), but now it is possible to define both absolute and relative thresholds for the benchmarks (as documented at https://swiftpackageindex.com/ordo-one/package-benchmark/1.21.3/documentation/benchmark/writingbenchmarks)
Features
1.21.3
1.21.3 (2024-01-10)
What's Changed
- docs(patch): Add "About Percentiles" page by @finestructure in #221
New Contributors
- @finestructure made their first contribution in #221
Full Changelog: 1.21.2...1.21.3
Contributors
Assets 2
1.21.2
1.21.1
1.21.0
1.21.0 (2024-01-08)
Reduce dependencies from 12->7;
Removing extras-json and instead use Foundations JSON - we have a Foundation dependency anyway and will hopefully soon move to the new swift-foundation.
Fold in Progress.Swift inline with the project instead of depending on Ordo tagged release version
Fold in BenchmarkClock to remove dependency on Ordo package-datetime, move to use CLOCK_BOOTTIME
Update NIO locks from upstream (will be removed whenever we get locking primitives in the standard library...).
Move Benchmarks to a separate embedded project a la SwiftNIO to allow it to use newer toolchain and remove dependencies
Remove DocC plugin dependency as it is done behind the scenes by SPI anyway
What's Changed
Full Changelog: 1.20.0...1.21.0
Contributors
Assets 2
1.20.0
1.20.0 (2023-12-21)
This release gives a significant performance boost for the benchmark result processing, baseline reading-parsing-exports etc, as the BenchmarkTool that is doing the heavy lifting now is built in release mode regardless of how the invocation of package benchmark was done.