chore: Improve CI benchmark speed #266
action.yml
on: pull_request
quick-tests
54s
Matrix: cross-compile-bench
deploy
0s
run-bench
10m 51s
Annotations
1 error and 11 warnings
run-bench
# :warning: **Performance Alert** :warning:
Possible performance regression was detected for benchmark.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold `1.30`.
| Benchmark suite | Current: ff02e98ce505f32af971de3dfb5c21f090a09d89 | Previous: 311fdb2eea6a319ed6348a7edbfd349d30068f9e | Ratio |
|-|-|-|-|
| `read_accel` | `551798` ns/iter (`± 60333`) | `218495` ns/iter (`± 7643`) | `2.53` |
| `read_gyro` | `547528` ns/iter (`± 24765`) | `218062` ns/iter (`± 9973`) | `2.51` |
| `read_pressure` | `476198` ns/iter (`± 74758`) | `189023` ns/iter (`± 9565`) | `2.52` |
| `read_temperature` | `238428` ns/iter (`± 1007`) | `94617` ns/iter (`± 5367`) | `2.52` |
| `set_pwm_enable` | `100601` ns/iter (`± 16634`) | `40284` ns/iter (`± 2638`) | `2.50` |
| `get_pwm_enable` | `114269` ns/iter (`± 7095`) | `45315` ns/iter (`± 2462`) | `2.52` |
| `set_pwm_channel_value` | `185550` ns/iter (`± 2616`) | `84917` ns/iter (`± 302`) | `2.19` |
| `set_pwm_freq_hz` | `354727` ns/iter (`± 88538`) | `137036` ns/iter (`± 782`) | `2.59` |
| `set_neopixel` | `378881` ns/iter (`± 27217`) | `263503` ns/iter (`± 491`) | `1.44` |
| `set_led` | `99849` ns/iter (`± 10790`) | `39334` ns/iter (`± 3244`) | `2.54` |
| `set_led_toggle` | `215072` ns/iter (`± 49342`) | `84986` ns/iter (`± 3787`) | `2.53` |
| `get_led` | `113845` ns/iter (`± 15015`) | `45515` ns/iter (`± 2709`) | `2.50` |
| `read_leak` | `247376` ns/iter (`± 51718`) | `98176` ns/iter (`± 5088`) | `2.52` |
This comment was automatically generated by [workflow](https://github.com/bluerobotics/navigator-rs/actions?query=workflow%3ATest%20all%20targets) using [github-action-benchmark](https://github.com/marketplace/actions/continuous-benchmark).
|
run-bench
Performance alert! Previous value was 218495 and current value is 551798. It is 2.5254490949449644x worse than previous exceeding a ratio threshold 1.3
|
run-bench
Performance alert! Previous value was 218062 and current value is 547528. It is 2.510882226155864x worse than previous exceeding a ratio threshold 1.3
|
run-bench
Performance alert! Previous value was 189023 and current value is 476198. It is 2.5192595610058035x worse than previous exceeding a ratio threshold 1.3
|
run-bench
Performance alert! Previous value was 94617 and current value is 238428. It is 2.519927708551317x worse than previous exceeding a ratio threshold 1.3
|
run-bench
Performance alert! Previous value was 40284 and current value is 100601. It is 2.4972942111011815x worse than previous exceeding a ratio threshold 1.3
|
run-bench
Performance alert! Previous value was 45315 and current value is 114269. It is 2.521659494648571x worse than previous exceeding a ratio threshold 1.3
|
run-bench
Performance alert! Previous value was 84917 and current value is 185550. It is 2.1850748377827762x worse than previous exceeding a ratio threshold 1.3
|
run-bench
Performance alert! Previous value was 137036 and current value is 354727. It is 2.588567967541376x worse than previous exceeding a ratio threshold 1.3
|
run-bench
Performance alert! Previous value was 263503 and current value is 378881. It is 1.4378621875272768x worse than previous exceeding a ratio threshold 1.3
|
run-bench
Performance alert! Previous value was 39334 and current value is 99849. It is 2.53849087303605x worse than previous exceeding a ratio threshold 1.3
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "benchmark-binary".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
benchmark-binary
Expired
|
3.27 MB |
|