Benchmarking coding agents on Databricks' multi-million line codebase
1–10 of 78 posts
Re: Benchmarking coding agents on Databricks' multi-million line codebase
#2Re: Benchmarking coding agents on Databricks' multi-million line codebase
#31) Many models are now competitive at the top tier, including open source. 2) GLM 5.2 in particular was a major step forward in open source coding agent performance, 3) Harnesses make a huge difference in cost-performance. 4) Cheaper per-token does not imply cheaper per-task.
Re: Benchmarking coding agents on Databricks' multi-million line codebase
#4Re: Benchmarking coding agents on Databricks' multi-million line codebase
#5Re: Benchmarking coding agents on Databricks' multi-million line codebase
#6Re: Benchmarking coding agents on Databricks' multi-million line codebase
#7I have experienced similar behavior between opus and haiku when benchmarking Dara engineering tasks. The “cheaper” model takes many more turns to figure out the task and this is without taking into account other important factors.
Another interesting behavior that I observed is that Haiku tended to cheat more maybe because it was having a harder time to find the root cause of the problem.
Benchmarking and evaluation of agentic systems is very interesting and if there’s one thing that someone should keep from the Databricks post is how important is for everyone to build and run their own.
Re: Benchmarking coding agents on Databricks' multi-million line codebase
#8The combined size of codebases for the underlying opensource products (Apache Spark etc) might be around 1M lines, I think. Why does the orchestration/management layer, that is "databricks", exceed the sizes of the core products?
Re: Benchmarking coding agents on Databricks' multi-million line codebase
#9Re: Benchmarking coding agents on Databricks' multi-million line codebase
#10> Databricks’ multi-million line codebase The combined size of codebases for the underlying opensource products (Apache Spark etc) might be around 1M lines, I think. Why does the orchestration/management layer, that is "databricks", exceed the sizes of the core products?