+1 improving conbench and the orchestration would free up aws credits and more importantly the time taken to fix outrages!
Velox used to use conbench but through a VD provided instance. I haven't seen any movement to set up an independent instance. Rok Mihevc <[email protected]> schrieb am Do., 4. Juni 2026, 16:38: > Hi Wes, > > Conbench is now at conbench.arrow-dev.org. I forked all repos to > arctosalliance github org in case VD deleted them on the way out. > Historical RDS db is preserved in the AWS account we migrated Arrow's CI > infra to. It's supported by donated AWS credits. > For orchestration buildkite.com/apache-arrow is still used and I even got > the old M1 mac mini from Mike. It's now in my rack running benchmarks > again. > > That said current design of the orchestration layer, api server and db is > somewhat costly and brittle. Downtime and adhoc fixes are common and I was > thinking about refactoring it somewhat to make it more maintainable. > > 1) If things become more maintainable and long term stable that'd be great. > I'm happy to collaborate on this. > 2) I'm only aware of arrow and arrow-go currently using it. > > Best, > Rok > > On Thu, Jun 4, 2026 at 4:20 PM Wes McKinney <[email protected]> wrote: > > > hi all, > > > > I saw that conbench.ursa.dev has been down and I had a need to set up > > some continuous project benchmarks, and was interested in doing > > development on Conbench (well, having my agents do development on > > Conbench), and was interested in the following: > > > > 1) is there interest in migrating the historical Arrow conbench data > > to a new server, has that been preserved somewhere? I'll probably > > rewrite the conbench backend in Go and give it a client CLI for > > submitting new data or querying old data. > > > > 2) are there other users of conbench (conbench/conbench) that anyone > > is aware of? I'd be done doing in-situ development in that repository > > or setting up a conbench-v2 project. > > > > No particular urgency but if anyone has opinions let me know! > > > > thanks, > > Wes > > >
