Implement LIKE in vortex instead of falling back to arrow#8709
Merged
CodSpeed HQ / CodSpeed Performance Analysis
failed
Jul 10, 2026 in 0s
3 benchmarks regressed
⚡ 8 improved benchmarks
❌ 3 regressed benchmarks
✅ 1619 untouched benchmarks
🆕 7 new benchmarks
⏩ 42 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Simulation | chunked_varbinview_canonical_into[(1000, 10)] |
154.6 µs | 189.6 µs | -18.48% |
| ❌ | Simulation | slice_empty_vortex |
339.4 ns | 397.8 ns | -14.66% |
| ❌ | Simulation | compact[(4096, 90)] |
779.7 ns | 867.2 ns | -10.09% |
| ⚡ | Simulation | rebuild_naive |
105.8 µs | 91.3 µs | +15.89% |
| ⚡ | Simulation | bitwise_not_vortex_buffer_mut[128] |
215.3 ns | 186.1 ns | +15.67% |
| ⚡ | Simulation | chunked_varbinview_into_canonical[(100, 100)] |
307 µs | 272.1 µs | +12.82% |
| ⚡ | Simulation | bitwise_not_vortex_buffer_mut[1024] |
275.6 ns | 246.4 ns | +11.84% |
| ⚡ | Simulation | chunked_varbinview_opt_canonical_into[(100, 100)] |
340.5 µs | 305.5 µs | +11.44% |
| ⚡ | Simulation | encode_varbin[(1000, 8)] |
160.7 µs | 144.7 µs | +11.02% |
| ⚡ | Simulation | encode_varbin[(1000, 4)] |
159 µs | 144.1 µs | +10.37% |
| ⚡ | Simulation | chunked_varbinview_opt_into_canonical[(100, 100)] |
389.7 µs | 353.8 µs | +10.15% |
| 🆕 | Simulation | ilike_contains |
N/A | 782.1 µs | N/A |
| 🆕 | Simulation | like_contains |
N/A | 155.3 µs | N/A |
| 🆕 | Simulation | like_exact |
N/A | 43.2 µs | N/A |
| 🆕 | Simulation | like_per_row_patterns |
N/A | 167.4 µs | N/A |
| 🆕 | Simulation | like_prefix |
N/A | 50 µs | N/A |
| 🆕 | Simulation | like_regex |
N/A | 623.3 µs | N/A |
| 🆕 | Simulation | like_suffix |
N/A | 65.3 µs | N/A |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing rk/native-like (436e600) with develop (2a58c67)
Footnotes
-
42 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. ↩
Loading