Managing AI Coding Costs at Scale
databricks.com
Managing AI Coding Costs at Scale
1–10 of 266 posts
Re: Managing AI Coding Costs at Scale
#2Really? Because removing it from my company has saved us over 2 million a year and we were able to speed up processing. The chargeback model for databricks is predatory at best.
Re: Managing AI Coding Costs at Scale
#3Careful. If you admit to using models that weren't trained by OpenAI or Anthropic then you might hauled in front of Congress: https://www.scmp.com/news/china/diplomacy/article/3362616/us...
Re: Managing AI Coding Costs at Scale
#4Really? Because removing it from my company has saved us over 2 million a year and we were able to speed up processing. The chargeback model for databricks is predatory at best.
I think you’ve misunderstood the article. It’s about how Databricks reduced their own costs, not about how adopting Databricks will reduce anyone else’s costs.
Re: Managing AI Coding Costs at Scale
#5Too bad their AI query generation is next to useless.
Re: Managing AI Coding Costs at Scale
#6Really? Because removing it from my company has saved us over 2 million a year and we were able to speed up processing. The chargeback model for databricks is predatory at best.
What did you move to and what type of workload, if I may ask?
Re: Managing AI Coding Costs at Scale
#7First time hearing of Omnigent. Anyone have experience using it?
Re: Managing AI Coding Costs at Scale
#8This approach seems fundamentally predicated on being able to evaluate coding agents on your own code by having domain specific evals. With that knowledge, you can trust the routing logic is actually improving/maintaining perf while reducing costs.
Without the insight into agent performance, any changes like this feel like a gamble to save $$ at the cost of developer productivity
I'm actually working on building generic repo-specific benchmarks at https://stet.sh ;)
Re: Managing AI Coding Costs at Scale
#9Yawn. Databricks and their half baked overly expensive platform.
Re: Managing AI Coding Costs at Scale
#10These seem like the obvious tweaks akin to "using a cheaper hosting platform". I think the real savings come from careful context control for programmatic agents, careful tool awareness and usage to reduce thrashing, distilling workflows into deterministic processes and, moat importantly, adding friction and boundaries for non-technical users who tend to burn tokens making insane asks like "analyze all documents and give me a summary".