创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

亚马逊用Strands Decider替代Sonnet分类工单

AI 总结

亚马逊工程师称,Amazon和AWS团队已在大规模内部工单分类中,以Strands Decider E4B决策模型取代Claude Sonnet 4.6。亚马逊测得两者效果相当,平均调用时间从4,215毫秒降至897毫秒,按公开标价估算成本降低约98%;这些数据及每年节省数百万美元的说法尚无独立验证。

深度见解

这一部署表明,对于固定选项的分类任务,专用决策模型可以替代通用大语言模型,并在亚马逊的测试中实现更低延迟、更少Token消耗和更低服务成本。

For a while, Amazon and AWS teams relied on Claude Sonnet 4.6 to label tickets in an internal system without breaking the bank.

Sonnet 4.6 fit the goldilocks choice of balancing intelligence with cost. Considering it dealt with one of the world’s largest internal ticketing systems, the nine month old model did well. However, two Amazon engineers recently swapped out Sonnet 4.6 for Strands Decider, a decision model we launched a month ago, that performed just as well at 98% less cost. This change will save millions of dollars of token costs in a year.

Carr and Mehul, who work on the internal ticketing system, walk through how this happened below.

Replacing an LLM’s job with a decision model

We had Sonnet 4.6 labeling tickets at enormous scale. The tickets could be customer escalations, capacity requests, automated alarms, security findings, or anything else across the company that needed to fit within 20 category types. The agent ran with a long system prompt on every ticket, generating JSON and reasoning against a fixed set of labels.

A decision model can’t generate text. It’s first given some state and a question with a set of options, then the decision model returns a probability for each option plus a confidence score. We saw this method fit perfectly with ticket labeling: the state is the ticket, the options are the label catalog.

#Amazon#AWS#Strands Decider E4B#Claude Sonnet 4.6#Gemma 4#Amazon SageMaker

原文约 4 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。