ci: add focused PR benchmark labels - #9018
Conversation
89eebfa to
77a7e5d
Compare
|
note that we probably dont want all of these labels, but I feel like a bit more than what we have on develop now would be nice? |
|
actually Im going to make them all disjoint, lets see how that works |
77a7e5d to
9cbc6da
Compare
9cbc6da to
2d3d02c
Compare
Signed-off-by: Connor Tsui <connor.tsui20@gmail.com>
2d3d02c to
c5173aa
Compare
Merging this PR will improve performance by 16.73%
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ⚡ | WallTime | cuda/bitpacked_u8/unpack/3bw[100M] |
351.5 µs | 301.1 µs | +16.73% |
Tip
Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.
Comparing ct/benchmark-labels (c5173aa) with develop (b15394a)
Footnotes
-
3 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩
|
Let's use bench-random-access, ra isn't straight obvious |
Adds four mutually exclusive PR benchmark triggers:
action/bench-raaction/bench-compressaction/bench-sql(no Vortex Compact)action/bench-sql-compact(only Vortex Compact)TODO after merge: delete the legacy
action/benchmark*labels, which remain temporarily for the currentdevelopdispatcher.