Benchmarks

Benchmark execution time: 2025-08-21 15:23:43

Comparing candidate commit ea9d9db in PR branch eliottness/remove-apache-equeue with baseline commit 5fad65d in branch main.

Found 5 performance improvements and 5 performance regressions! Performance is the same for 5 metrics, 0 unstable metrics.

scenario:BenchmarkCaptureStackTrace/10-24

• 🟥 allocated_mem [+1.372KB; +1.380KB] or [+17.578%; +17.690%]
• 🟩 allocations [-17; -17] or [-32.075%; -32.075%]

scenario:BenchmarkCaptureStackTrace/100-24

• 🟥 allocated_mem [+6.286KB; +6.360KB] or [+10.530%; +10.654%]
• 🟩 allocations [-110; -110] or [-33.742%; -33.742%]

scenario:BenchmarkCaptureStackTrace/20-24

• 🟥 allocated_mem [+2.098KB; +2.112KB] or [+15.728%; +15.833%]
• 🟩 allocations [-26; -26] or [-31.707%; -31.707%]

scenario:BenchmarkCaptureStackTrace/200-24

• 🟥 allocated_mem [+15.802KB; +15.890KB] or [+13.454%; +13.529%]
• 🟩 allocations [-212; -212] or [-33.758%; -33.758%]

scenario:BenchmarkCaptureStackTrace/50-24

• 🟥 allocated_mem [+3.795KB; +3.828KB] or [+12.621%; +12.730%]
• 🟩 allocations [-58; -58] or [-33.333%; -33.333%]

/merge

View all feedbacks in Devflow UI.

2025-08-21 13:06:49 UTC ℹ️ Start processing command /merge

2025-08-21 13:07:02 UTC ℹ️ MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

2025-08-21 15:35:09 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in main is approximately 14m (p90).

2025-08-21 15:47:00 UTC ℹ️ MergeQueue: This merge request was merged

@eliottness The benchmark results are very curious. I think we'll have to optimize the implementation, as it feels like eapache/queue/v2 did something interesting that lead to less memory.