freef4ll
commented
11 months ago Docker scripts have been updated, but having issues with thresholds:
+ export PATH=/root/.tools:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
+ PATH=/root/.tools:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
+ cd Benchmarks
+ swift package --disable-sandbox --scratch-path .build/5.8/ --allow-writing-to-package-directory benchmark --format metricP90AbsoluteThresholds --path Thresholds/5.8/
error: 'benchmarks': unknown package 'swift-prometheus' in dependencies of target 'PrometheusBenchmarks'; valid packages are: 'code', 'package-benchmark'Split the benchmark code into the benchmark definition and separate files for the benchmarks under test
I have done this, and there are 2 implementations for Counter to see on which is the preferred one (one captures the allocation but is slower due to return of the closure).
FranzBusch
hassila
ktoso
Motivation
Adding benchmark tests in order to aid development and avoid performance regressions.
Benchmark is added in the same fashion as for swift-nio and swift-certifcates.
Modifications
Benchmarks are added for incrementing a counter, gauge, histogram and an export of 5000 metrics from the esystem.
How to execute benchmark
In Xcode can open the project like and use Instruments to profile:
Result
Benchmarks are available, and performance difference between v1 is great which only managed to increment 2-3k times per second.