3073 次浏览 · 24 赞 · 3 转发 (收录时)
Artificial Analysis 将每项任务耗时作为其 API 基准测试的头条指标
发生了什么
Artificial Analysis 更新了其 API 性能基准测试,将每项任务耗时设为头条指标,衡量模型完成一项任务所需的时间,而非模型流式输出 token 的速度。该基准测试涵盖约 1,000 个无服务器端点,现已纳入智能体工作负载。Artificial Analysis 报告称,对若干模型而言,默认的努力程度设置可缩短任务耗时并降低成本,但这些模型在 Intelligence Index 上的得分也更低。
接下来读什么
查看这件事的完整进展Artificial Analysis Makes Time per Task Its Headline API Benchmark MetricAnnouncing the next version of Artificial Analysis API Performance Benchmarking: Time per Task is now our headline performance metric, measuring how long a model takes to complete a task rather than how fast it streams
The update applies to the ~1,000 serverless endpoints we benchmark multiple times a day for speed, latency and caching.
Key changes:
➤ Time per Task is now the headline metric to compare models: as workloads become more agentic, the time to complete a task matters more than speed per token. A model that is fast per token but verbose can take longer than a slower model that uses fewer tokens. Time per Task divides a model's output tokens per Intelligence Index task by its End-to-End Output Speed.
➤ End-to-End Output Speed covers the full request: speed is now measured from sending the request to receiving the final token. That includes the wait before the first token (prefill, and reasoning for models that hide it) as well as generation. Output tokens now come from each provider's API-reported counts instead of the o200k_base tokenizer, and we monitor for discrepancies in reported counts.
➤ Agentic workloads are now part of every measurement: we benchmark short, document-length and long-context prompts, plus multi-turn sessions across coding and knowledge work. Headline figures are the average across these workloads over the past 5 days.
➤ API default effort is now tracked alongside highest effort: most developers run models at the effort level each lab sets as its API default, so we now benchmark key models at that setting as well as at their highest effort. Effort names are not comparable across labs, so we use each lab's own default rather than one shared setting.
Key takeaways:
➤ OpenAI models make up most of the Intelligence vs. Time per Task Pareto frontier despite slower output speeds: across effort levels, GPT-6 Astra and GPT-6.1 Sol hold the frontier from ~45 to ~55 on the Intelligence Index. At max effort, GPT-6 Astra runs at 51 tokens/s but finishes a task in ~17 minutes, against ~26 for Claude Opus 5.5 (max, 111 tokens/s) and ~29 minutes for Gemini 4 Carbon (high, 71 tokens/s), because it uses ~50k output tokens per task against ~120k to ~170k.
➤ API default effort cuts Time per Task by ~3 to 5x and Cost per Task by ~2 to 4x for GPT-6 Astra, GPT-6.1 Sol and Claude Opus 5.5: all three default to medium effort, which scores ~5 to 11 points lower on the Intelligence Index in exchange. Claude Opus 5.5 falls from ~26 minutes and $10.04 per task at max to ~6.8 minutes and $2.45 at medium effort.
➤ Endpoints that optimize for decode speed alone see the largest drop in End-to-End Output Speed: high decode speeds can come at the cost of latency, for example by queuing requests to run at lower batch sizes, or by holding output and sending it in a single burst. Both lengthen the wait before the first token, which End-to-End Output Speed now counts.
这件事到目前为止
Artificial Analysis updated its API performance benchmark to make Time per Task the headline metric, measuring how long a model takes to complete a task rather than how quickly it streams tokens. The benchmark covers about 1,000 serverless endpoints and now includes agentic workloads. Artificial Analysis reports that default effort settings reduce task time and cost for several models while lowering their scores on the Intelligence Index.
每天一封,跟上 AI 的重要变化
模型发布、价格变化、算力进展,附原始来源。免费,确认后开始发送,随时一键退订。 看一份往期日报 · 2026-11-04
