chore: release v0.0.21#138
Merged
Merged
Conversation
sw-release-bot
Bot
force-pushed
the
release-plz-2026-05-15T10-14-50Z
branch
3 times, most recently
from
53289f3 to
743cb47
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
sw-release-bot
Bot
force-pushed
the
release-plz-2026-05-15T10-14-50Z
branch
2 times, most recently
from
a753d07 to
a2d95e0
Compare
![sw-release-bot[bot]](https://avatars.githubusercontent.com/u/228206483?s=60&v=4){kind=small}
Author
There was a problem hiding this comment.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'structured-zstd vs C FFI (x86_64-gnu)'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.30.
| Benchmark suite | Current: dc869d6 | Previous: 1e0f695 | Ratio |
|---|---|---|---|
compress/level_22_btultra2/small-4k-log-lines/matrix/c_ffi |
0.113 ms |
0.067 ms |
1.69 |
compress/level_22_btultra2/decodecorpus-z000033/matrix/c_ffi |
282.375 ms |
171.961 ms |
1.64 |
compress/level_22_btultra2/low-entropy-1m/matrix/c_ffi |
1.705 ms |
1.184 ms |
1.44 |
This comment was automatically generated by workflow using github-action-benchmark.
CC: @polaz
sw-release-bot
Bot
force-pushed
the
release-plz-2026-05-15T10-14-50Z
branch
5 times, most recently
from
9d084e9 to
b95c881
Compare
sw-release-bot
Bot
force-pushed
the
release-plz-2026-05-15T10-14-50Z
branch
from
b95c881 to
dc869d6
Compare
This was referenced May 17, 2026
polaz
added a commit
that referenced
this pull request
May 17, 2026
… shards finish (#153) The bench-matrix runs seven strategy shards per target. The heaviest shards exceed the previous per-target caps on every main push: * lazy shard runs 11 levels (5..15) sequentially through one bench binary invocation. On any target this takes 25-30+ minutes, hitting the cap before the benchmark frame even starts on the last level. * fast shard runs 8 levels (-7..-1, 1). On i686-gnu (32-bit, ~30% slower) this consistently exceeds the previous 30m cap. * btultra2 shard runs 3 expensive levels (20..22). On i686-gnu the matcher passes alone push it past 30m. When a single shard hits its job timeout the whole CI run is marked failed, so benchmark-aggregate and benchmark-pages never run and the dashboard at https://structured-world.github.io/structured-zstd/dev/bench/ gets no new data point for that commit. This affected every main push today (#148, #151, #138 → v0.0.21 release). Bump per-target timeout_minutes: x86_64-gnu 25 -> 45, i686-gnu 30 -> 60, x86_64-musl 25 -> 45. The 32-bit target gets a higher absolute cap because its bench loop is consistently ~30% slower. Closes #152
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 New release
structured-zstd: 0.0.20 -> 0.0.21Changelog
This PR was generated with release-plz.