SShortSingh.
Back to feed

Vendor's 200x Speed Claim Shrinks to 3–12x Under Real Workload Testing

0
·45 views

A software team tested TypeSafe AI's model 'Jev' against their existing open model using a real production task: classifying email accounts on an admin dashboard. End-to-end, the new model proved 12x faster at the median, narrowing to roughly 3x once accounting for unnecessary output from the old model, and 7x cheaper — primarily because outbound tokens are free on the new platform. The team admits they produced two confident but incorrect benchmark figures before arriving at valid results, including repeating the very measurement error they had previously criticized the vendor for. The most meaningful finding was not speed but consistency: the new model showed just 38ms of latency variance compared to 2,353ms on the old one, eliminating parse failures that had been causing error pages. The team concludes that benchmarks are only useful when run on your own workload, close to production, with a reliable correctness check that does not rely on another model's judgment.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingHacker News ·

Google Introduces Gemini Omni 1.2 Flash for Developers

Google has announced Gemini Omni 1.2 Flash, a new model release aimed at developers. The announcement was published on the company's official blog under its innovation and AI section. The source material available provides only the headline and link, so details such as specific capabilities, benchmarks, and pricing are not confirmed here. The story gained early traction on Hacker News, where it has received six points and no comments so far.

0
ProgrammingDEV Community ·

Audit of 11 Voice AI Engineering Teams Highlights Latency and Compliance Hurdles in Healthcare

A DEV Community analysis reviews 11 engineering teams building voice AI for healthcare, comparing their underlying technology stacks. It argues that a weekend prototype quickly breaks down in clinical settings due to four challenges: response latency, HIPAA Business Associate Agreement requirements, data access boundaries, and carrier spam flagging. The piece notes that natural phone conversation requires total turn-taking latency under roughly 800 milliseconds, which depends on a streaming pipeline spanning telephony, speech-to-text, the language model, and voice synthesis. Teams are compared by primary voice stack, telephony gateway, typical entry cost, and location, with specialties ranging from AWS telephony to hospital EHR integration.

0
ProgrammingDEV Community ·

AutoMode: free Claude Code mod that auto-picks model and effort per prompt

A developer released AutoMode, a free, MIT-licensed mod for Claude Code that selects the model and reasoning effort for each prompt. Two small Haiku judges first estimate task difficulty, then route simple questions to cheaper models and riskier work such as auth or migrations to Opus. The tool also offers a multi-agent workflow for larger jobs, with subagents handling discovery, planning, building, verification and review. In the author's five mixed-session benchmark, AutoMode cost about 51% less than Claude Code on Opus while all tasks still passed. The savings were smallest on long coding sessions without intervening questions, where it runs mostly on Sonnet.

0
ProgrammingDEV Community ·

Weaker model panels can still flag wrong MMLU answer keys, with strength mattering more than size

Researchers at Munim, Inc. tested which AI models best identify mislabeled answers in the MMLU benchmark, using pre-registered, open code. They compared a rule based on the top 10 most accurate models with a signal using all 78 models, measuring item discrimination. Against expert labels in MMLU-Redux 2.0, the discrimination signal performed slightly worse than the top-10 rule, while the two together gave the most precise short list. Splitting models into panels by accuracy showed that weaker panels catch roughly the same wrong keys but add many more false flags. The team concluded that stronger panels are preferable, though cheaper older models still perform reasonably when reviewed under a fixed budget rather than a vote threshold.