← All AI Engineer talks

AI Engineer World's Fair 2025

Trends Across the AI Frontier

Read the talk

Choosing Models Across the AI Frontier

Model intelligence is only one constraint: reasoning tokens, sequential latency, open weights, cost and inference speed determine what an application can actually do.

From a talk by Micah Hill-Smith and George Cameron

Before you start: Familiarity with language-model APIs, tokens and basic inference terminology will help you follow the comparisons.

What are you optimizing for?

How should you compare AI systems when model intelligence, API performance and hardware performance measure different things? Artificial Analysis benchmarks all three: model capability, endpoint speed and cost, and the accelerators serving inference. Its coverage extends beyond language to vision, speech, image generation and video generation. At the time of George Cameron’s presentation, the company covered more than 150 models, published most results freely, and offered reports and enterprise subscriptions to support production adoption. Those separate measurements provide the basis for choosing a model that fits an application.

0:450:58
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

0:45 · section reference included

Intelligence is only one frontier

The launch of ChatGPT and GPT-3.5 began the historical arc: more releases followed, from more labs, with increasingly crowded competition at the frontier. In the presentation’s ranking, o3 led, followed closely by o4-mini with high reasoning. Other leading models included DeepSeek-R1, Grok 3 Mini with high reasoning, Gemini 2.5 Pro, and Claude 4 Opus Thinking.

Step-line chart of the Artificial Analysis Intelligence Index by release date, with colored lines for six AI labs and labels for recent models.
Frontier model intelligence over time shows increasingly close competition among AI labs.

The ranking used the Artificial Analysis Intelligence Index, a weighted composite of seven evaluations intended to provide a generalist view of capability. These are historical measurements using that seven-evaluation index and the configurations and prices reported in the talk; the current methodology and live rankings have since changed.

The most intelligent model is not always the right model. Accessing intelligence entails trade-offs, so a useful comparison must examine several frontiers. The progression here is reasoning versus non-reasoning models, open weights versus proprietary models, cost, and speed. Each changes the set of applications that is practical to build.

1:542:16
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

1:54 · section reference included

Reasoning buys capability with more tokens

Plot Intelligence Index scores against the output tokens required to complete the evaluations, and two groups emerge. Non-reasoning models use fewer output tokens but achieve lower measured intelligence in this comparison. Reasoning models achieve higher scores while generating substantially more tokens. The additional generation matters twice: it adds expense and extends the time required to finish a request.

The reported evaluation runs show the scale of that difference. GPT-4.1 required millions of output tokens; the reasoning models required tens or hundreds of millions.

ModelOutput tokens for the full Intelligence Index run
GPT-4.17 million
o4-mini, high reasoning72 million
Gemini 2.5 Pro130 million

These are totals across the seven evaluations, not the length of an individual response. Cameron describes an order-of-magnitude difference between reasoning and non-reasoning models—large enough that token volume must be treated as an application constraint alongside capability.

4:064:27
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

4:06 · section reference included

Measure the wait for a complete answer

Across Artificial Analysis’s tested API requests, GPT-4.1 had a median full-response latency of 4.7 seconds; o4-mini with high reasoning took over 40 seconds in the reported comparison. The slide uses a 500-output-token workload, including reasoning time. That is roughly an order of magnitude more waiting. Full-response latency measures the wait for the complete answer, rather than time to first token or the rate at which tokens arrive. The slide separates input processing, thinking and output generation, making visible why a fast output stream alone does not describe the entire interaction.

Stacked bar chart comparing model response times, with a shaded reasoning-model region and a purple 9X comparison arrow.
End-to-end response times separate input processing, thinking and output generation.

That wait affects enterprise chatbots as well as consumer applications. A user does not necessarily need the strongest reasoning model for every interaction, particularly when responsiveness is part of the product’s value. Cameron invokes Facebook studies of latency-related user drop-off as supporting motivation, without giving a specific study or numerical result. The actionable question is whether the additional capability justifies the delay for the interaction being built.

5:536:13
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

5:53 · section reference included

An agent multiplies per-call latency

For an agent making successive requests, latency accumulates along the chain. Cameron uses 30 sequential queries as a plausible workload. Faster responses can change the workflow itself: instead of merely completing the same 30 calls sooner, an application might fit something closer to 100 calls into its waiting budget.

In the illustrative agent calculation, 30 sequential calls at 10 seconds each take 300 seconds, or five minutes; at one second each, they take 30 seconds. This is arithmetic for a sequential workload, not a measured agent benchmark. A small TypeScript calculation makes the dependency explicit:

typescript

const calls = 30;

const scenarios = [
  { secondsPerCall: 10 },
  { secondsPerCall: 1 },
];

console.table(
  scenarios.map(({ secondsPerCall }) => {
    const totalSeconds = calls * secondsPerCall;
    return {
      calls,
      secondsPerCall,
      totalSeconds,
      totalMinutes: totalSeconds / 60,
    };
  }),
);

The calculation isolates model-call time. An actual workflow must also account for whatever happens between calls, but the sequential dependency alone already creates a substantial difference.

A contact-center application makes the product constraint concrete: a 30-second wait might be acceptable, while five minutes on the phone could make the interaction unusable. Likewise, imagine waiting five minutes every time you invoked a function in Google. The latency budget determines which workflows are viable, so measure the trade-off in the application rather than assuming a higher intelligence score will compensate for the wait.

6:577:17
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

6:57 · section reference included

Open weights close the capability gap

The open-weights frontier has moved unevenly. Around the release of GPT-4, Llama 65B and Llama 2 70B were substantially behind proprietary capability. Later releases such as Mixtral 8x7B and Llama 405B narrowed the gap. Then o1 pulled ahead again in late 2024, reopening the separation.

DeepSeek-V3 arrived in December, prompting Cameron to interrupt his Christmas holiday to read its technical report. R1 followed in January. By the presentation, Cameron reported that the recent R1 release was only a couple of Intelligence Index points behind the leading models. The progression matters: open weights were catching up not only to an older proprietary generation, but also to the newer reasoning frontier.

China-based labs led both the reasoning and non-reasoning open-weights rankings shown in the talk, with DeepSeek first in each. Alibaba’s Qwen 3 series followed in reasoning. Meta and NVIDIA’s Nemotron fine-tunes of Llama were also competitive. The resulting choice was broader than a single leading proprietary API: open-weights models had become close contenders on the measured capability axis.

8:258:29
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

8:25 · section reference included

Compare the cost of completing the work

Cost changes what can be built just as latency does. At the prices used for the presentation’s evaluations, o3 cost almost $2,000 to complete the Intelligence Index. The cost of running evaluations had become substantial enough to attract TechCrunch coverage. Cameron then compared GPT-4.1 and GPT-4.1 Nano with more expensive reasoning models:

Comparison on the Intelligence Index workloadReported cost difference
GPT-4.1 versus o1Roughly 30 times cheaper
GPT-4.1 Nano versus o3More than 500 times cheaper

The denominators differ: GPT-4.1 is compared with o1, while Nano is compared with o3. These ratios describe the evaluation-suite workload.

An application’s cost structure may therefore determine both which model it can use and how many times it can call that model. Cameron pushes the idea toward agents, suggesting that hundreds of inexpensive calls could cost less than one expensive call. That is a design possibility to investigate, not a universal per-query ratio established by the suite totals; actual prompts, responses and reasoning lengths determine the bill.

Price per token is only half of the cost calculation. The other half is how many tokens the model consumes and produces. In the billing behavior discussed here, reasoning tokens count as output tokens even when the provider does not expose their contents. A model can therefore have an attractive advertised price per million tokens and still be expensive to use because it generates much more internal reasoning or a longer answer.

Verbosity also varies among non-reasoning models. Compare the cost of completing the same application workload, including billed reasoning tokens, instead of assuming that every model will generate the same amount of text. The evaluation-suite comparison is useful precisely because it measures token quantity and token price together.

10:2610:40
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

10:26 · section reference included

Hold capability constant and watch cost fall

To study cost over time, group models into intelligence bands. This asks what it costs to access a comparable level of capability, rather than what the newest frontier model costs. Cameron reports that the cost of accessing GPT-4-level intelligence fell by more than 100 times from mid-2023 to the presentation. Declining costs appeared across the plotted quality bands.

Even a newly reached band could become cheaper quickly. Cameron reports that the cost of accessing the intelligence band reached by o1-mini in late 2024 halved within a few months. That creates a useful planning exercise: what would you build if the current inference cost were no longer a barrier? An application whose economics fail today might become feasible six months later. That possibility is a reason to examine future cost scenarios, not a guarantee that a particular project’s economics will work on that schedule.

12:5013:07
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

12:50 · section reference included

The same capability arrives faster

The speed frontier measures output tokens per second. Because capability and speed often trade off, intelligence bands again provide the useful comparison: how quickly can an application receive output at a given capability level? The plotted bands all show rising output speed.

Cameron recalls GPT-4 generating about 40 output tokens per second in 2023 and reports access to comparable intelligence at over 300 tokens per second by the presentation. The practical memory is familiar: waiting for ChatGPT to finish emitting code before copying it into an editor and trying it. Faster generation shortens that wait even when the model is not performing an extended reasoning step.

Several changes contribute to faster inference:

  • Model sparsity: Mixture-of-experts models activate only a fraction of their parameters during inference. Less computation per token can mean faster generation, and increasingly sparse models extend that advantage.
  • Smaller, more capable models: Distillation helps smaller models, including the cited 8B examples, deliver more intelligence without requiring the same model size.
  • Inference software: FlashAttention and speculative decoding are two named optimization techniques.
  • Hardware: The progression from A100 to H100 and then B200 systems provides another source of improvement.

Cameron reports that newly published Artificial Analysis B200 benchmarks exceeded 1,000 output tokens per second. The talk does not specify the model or workload for that result, so it is not a controlled hardware comparison with the earlier GPT-4 figure. Specialized accelerators from Cerebras, SambaNova and Groq add further options.

Step-line chart of model output speed over release dates, grouped by intelligence bands, beside a panel listing sparsity, smaller models, inference software optimizations and hardware improvements.
Output speed rises across intelligence bands, with four key inference drivers listed alongside.
14:0914:23
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

14:09 · section reference included

Efficiency can increase the appetite for compute

Lower costs at a fixed intelligence level, better hardware and greater system output throughput all improve efficiency. Yet Artificial Analysis’s house view is that aggregate compute demand will continue to rise. Efficiency gains change what is affordable, while the desired scale of model use continues to expand.

Larger models are one driver. Cameron points to DeepSeek having more than 600 billion total parameters, explicitly correcting himself from active to total parameters. That distinction matters for sparse models: the full parameter count and the amount activated during inference are different quantities.

The other multipliers follow directly from the earlier comparisons. Demand for greater intelligence encourages more inference-time reasoning, which consumes additional compute. Agents turn one user task into sequences of 20, 30 or more than 100 model requests. More capable models, longer reasoning and more calls per task can absorb the savings from cheaper, faster inference. The closing expectation is therefore rising net compute demand—a house view about how these forces combine, rather than a quantified forecast.

16:3416:38
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

16:34 · section reference included

Resources

From the talk

Updates since the talk

Read the complete timestamped transcript
  1. 0:00

    [upbeat music] Hi, everyone.

  2. 0:22

    I'm George, co-founder of Artificial Analysis. A quick background to who we are before we dive into things.

  3. 0:32

    Do you see that? We see it here.

  4. 0:36

    Sorry, I think my clicker's not working. Click.

  5. 0:45

    Oh, there we go. Great. So a quick background to who we are. We're a leading independent AI benchmarking company. We benchmark a broad spectrum across AI. So we benchmark models for their intelligence.

  6. 0:58

    We benchmark API endpoints for their speed, their cost. We also benchmark, uh, hardware and all the AI accelerators out there. Uh, and we also benchmark a range of modalities, not just language, but also vision, speech, image generation, video generation.

  7. 1:17

    And we publish essentially nearly all of it, uh, for free on our website, artificialanalysis.ai, whereby we benchmark over a hundred and fifty different models, uh, across a range of metrics.

  8. 1:32

    We also publish reports, many of which are publicly accessible, and we also have, uh, a subscription for enterprises looking to, uh, enter, uh, or bring AI to production in their environments, um, in an efficient, uh, and effective way.

  9. 1:54

    Let's start off with AI progress. Let's set the scene. So it's been a crazy two years. I think that we've all felt it in this room, whereby OpenAI, uh, kicked off the race, uh, with the ChatGPT and GPT-3.5 launch, and since then, it's only gotten more hectic.

  10. 2:16

    There's been f-- more and more, uh, model releases by more and more labs pushing the AI frontier.

  11. 2:26

    So the current state now of frontier AI intelligence. I think this will be-- this order of models will be familiar to a lot in this room. o3 is the leader, but followed closely by o4-mini with reasoning mode high.

  12. 2:40

    DeepSeek-R1, the release in the last week or two. Grok 3 Mini, reasoning high. Gemini 2.5 Pro. Claude 4 Opus Thinking.

  13. 2:53

    This benchmark is our Artificial Analysis Intelligence Index. It's made up of a composite-- it's a composite index of seven evaluations, which we then weight to develop our Artificial Analysis Intelligence Index, which just provides a generalist perspective on the intelligence of these models.

  14. 3:17

    We all have an understanding of what f-frontier AI intelligence is, but what I want to explore with you today is that there's more than one frontier in AI. There's trade-offs to accessing this intelligence.

  15. 3:30

    You shouldn't always use the leading, most intelligent model. And so what we wanna do is we wanna explore the different frontiers out there, and as an AI benchmarking company, we're gonna bring some numbers to the fore to help you reason about this.

  16. 3:46

    First, we'll be looking at reasoning models. Next, we'll be looking at the open weights frontier. Third, the cost frontier. And lastly, the speed frontier. There's other frontiers out there that we benchmark, but we'll focus on these key ones today.

  17. 4:06

    Starting with reasoning models. What we've done here is we've taken our intelligence index and looked at that relative to the output tokens used to run the intelligence index. So we've measured all of how many tokens each model took to run our seven evaluations, and we've plotted it on this chart.

  18. 4:27

    And you can see two distinct groups. It's helpful to think about these separately. So non-reasoning models, which offer less intelligence but, uh, require fewer output tokens.

  19. 4:40

    And reasoning models, which use more output tokens but offer greater intelligence.

  20. 4:45

    And the more out-- this is important to look at because more output tokens comes with trade-offs, both for request latency as well as cost. We're gonna bring some numbers to draw that out and look at the real differences here.

  21. 5:01

    Starting with output tokens and the verbosity of these models, just how yappy these reasoning models are. We can see that there's an order of magnitude difference between reasoning and non-reasoning models.

  22. 5:17

    It's not just that feeling, "Oh, this is taking a long time." It's real. It's an order of magnitude. So between GPT-4.1, it c-- uh, it required seven million tokens to run our intelligence index evaluations.

  23. 5:31

    But then o4-mini-high took seventy-two million tokens. And the yappiest of them all, Gemini 2.5, uh, Pro, took a hundred and thirty million tokens to run our intelligence index.

  24. 5:44

    And as mentioned, this has implications for cost as well as end-to-end latency responsiveness.

  25. 5:53

    So looking at latency, we benchmark the API latency of how long it takes to receive a response when accessing these models via their APIs. Here we can see that GPT-4.1 on median across our request took four point seven seconds to return a full response.

  26. 6:13

    o4-mini-high took over forty seconds, roughly another ten x or order of magnitude increase. This has implications for applications and uses which require responsiveness, even enterprise, uh, kind of chatbots.

  27. 6:31

    You don't always reach for o3 in ChatGPT.

  28. 6:36

    And it-- And, you know, Facebook's done a lot of studies on this where they've looked at the-- for consumer apps, where they've looked at, uh, user drop-off by latent-- uh, application latency, which clearly demonstrate this.

  29. 6:49

    Sorry, do you mind if we jump back a slide?

  30. 6:57

    And it also has up, uh-- implications for how we're building. So I think particularly with agents whereby thirty, uh, queries in succession is not uncommon. It has m- it's a multiplier effect on the latencies, uh, for your application and how you can build.

  31. 7:17

    If you have faster responses, maybe you can make that thirty, uh, one hundred queries, for instance. And so putting numbers to that, in terms of agents, thirty is normal.

  32. 7:27

    And so even less than the o4-mini, maybe you're at ten seconds for a reasoning model. If you're running thirty queries, that's three hundred seconds that a user might be waiting for a response or an application might be waiting for a response.

  33. 7:40

    That's five minutes. If with the order of magnitudes that we're dealing with here, if that ten seconds was one second, then those thirty queries takes thirty seconds. Thirty seconds versus five minutes impacts what you can build.

  34. 7:55

    Think of a contact center, uh, application. That might-- maybe thirty seconds is okay there, but five minutes, uh, definitely not. Who likes waiting on the phone, uh, that long?

  35. 8:05

    Or imagine if you had to, uh, use Google, and each time that you wanted to use a function, it took five minutes. This impacts how we can build with these models.

  36. 8:15

    And so I think bringing numbers to these trade-offs is really important. I'd encourage everybody, uh, to measure them.

  37. 8:25

    Next, we're gonna move to the open weights frontier.

  38. 8:29

    Around the time of GPT-4, there was a huge delta in terms of open weights intelligence versus proprietary intelligence.

  39. 8:40

    Llama 65B or Llama 2 70B wasn't close to the intelligence of GPT-4. What I'd like to show here is where we plot our intelligence index by release date is that that gap had closed until with, with great models like Mixtral 8x7 and, uh, Llama 45B.

  40. 9:02

    But o1 broke away in late twenty twenty-four.

  41. 9:09

    But then, of course, I think we remember DeepSeek released V3, I think December twenty-sixth. Ruined some of my Christmas holiday plans. [laughs]

  42. 9:20

    Had to tell my family, "I, I need to go read this paper. It's really exciting."

  43. 9:26

    And then, of course, R1 in January. The gap between open-weights intelligence and proprietary model intelligence is less than it's ever been, particularly with the recent R1 release in the last couple of weeks, which is only a couple of points different in our intelligence index to the leading models.

  44. 9:49

    You can't talk about open weights intelligence without talking about China. The leading open weights models across both reasoning models and non-reasoning models are from China-based AI labs. DeepSeek's leading in both.

  45. 10:06

    Alibaba with their Qwen three series is leading-- is coming in second in reasoning.

  46. 10:13

    But you also have other labs such as Meta, uh, and NVIDIA with their Nemotron fine-tunes of Llama coming in close as well.

  47. 10:26

    Let's look at the cost frontier. This is really important, and I think similar to reas-- to, uh, end-to-end latency impacts what you can build. So bringing some numbers here, we can really see these order of magnitudes play out.

  48. 10:40

    So o3 cost us almost two thousand dollars to run our intelligence index. TechRun actually wrote an article about how much money we were, we were spending on running evals.

  49. 10:52

    We di- we didn't wanna read it. You can see four point one, a great model. It's thirty times roughly cheaper in terms of, uh, the cost to run our intelligence index compared to o1.

  50. 11:08

    And four point one Nano, over five hundred times cheaper to run our intelligence index than o3.

  51. 11:16

    You should think about these when building applications. The kinda co- uh, cost structure of your application might dictate what you can use here

  52. 11:25

    and how you use them. Those thirty, uh, sequential, uh, API calls for your agentic application could be, uh, five hundred and still be cheaper than an o3 query.

  53. 11:42

    A key point to note here with this cost to run intelligence index and why we don't just look at the per token price is that, and the labs maybe don't want you to think this way, [laughs] but you're paying for the cost per token, but then you're also paying for how verbose the models are.

  54. 11:59

    All the reasoning tokens that are output when these models are in their thinking mode.

  55. 12:06

    You pay for those as output tokens, even if some of the labs hide them. And so you need to think about this and measure it in your application, not-- and benchmark not just by the cost per million tokens, but also considering how many reasoning tokens there are and how verbose these models are.

  56. 12:26

    You can see even amongst the non-reasoning models, there's big differences between how verbose these models are in responses.

  57. 12:35

    So for instance-- Ah, we'll go to the next slide.

  58. 12:42

    Do you mind if we go back one, please?

  59. 12:50

    So what we've done here is we have-- now-- we're now gonna look at the trends in terms of cost. And so what you can see here is we've bucketed models by how intelligent they are, intelligence, uh, bands, if you will.

  60. 13:07

    And what we can see here is that accessing GPT-4 level of intelligence has fallen over a hundred times since mid '23.

  61. 13:18

    This is the case across all quality bands.

  62. 13:22

    You can see that even when a new quality band, a new frontier is reached, o1-mini in late '24.

  63. 13:30

    Quickly, within only a few months, the cost of accessing that level of intelligence halved. This is moving quickly. And so what I would say to you is when building applications, think about what if cost wasn't a barrier when you're building.

  64. 13:47

    It's a, it's a very important kinda cost, uh, exercise because it might well be that if you build for a cost structure that doesn't work now, then maybe in six months' time that will be, uh, possible and it will be, uh, feasible.

  65. 14:09

    Next, we're gonna look at the speed frontier. So this is how quickly you're receiving tokens, the output speed, output tokens per second that you're receiving after sending an A- API request.

  66. 14:23

    This has been increasing and has increased dramatically since early '23 as well. So similarly, we've-- because there's a trade-off typically between intelligence and speed, we've grouped models into certain buckets.

  67. 14:39

    And we can see here that they've all increased in terms of how quickly you can access a level of intelligence.

  68. 14:47

    So 4o, I believe, was around forty output tokens per second. Now you can access-- That was in 2023. Who remembers hitting-- It wasn't a reasoning model, hitting Enter in ChatGPT and just waiting for it to output, especially code, which you wanna just copy straight into your editor and, you know, hit Run [laughs] See if it works.

  69. 15:11

    Now you can access that level of intelligence at over three hundred tokens per second. A few drivers here that I'll go through. It's not the focus of the talk, but important to, to reference.

  70. 15:21

    Model sparsity, so we're seeing more MoEs, Mixture of Experts models, and they activate only a proportion of, uh, parameters at inference time. Less compute per token, which means it can go faster, essentially.

  71. 15:39

    And MoEs were around back then, but they're getting more and more sparse. A smaller proportion of active parameters. Next, smaller models. Smaller models are getting more intelligence, uh, intelligent, particularly with distillations, you know, 8B distillations, et cetera.

  72. 15:57

    Inference software optimizations like FlashAttention and speculative decoding.

  73. 16:04

    And lastly, hardware improvements. So H100 was faster than A100. Now that we've recently launched benchmarks of the B200 on our Artificial Analysis website, and it's getting over a thousand output tokens a second.

  74. 16:18

    Think about that relative to the forty output tokens per second of GPT, uh, four in '23.

  75. 16:25

    There's also specialized, uh, accelerators like Cerebra, SambaNova, Groq.

  76. 16:34

    I wanna share a house view here to frame things.

  77. 16:38

    Yes, things are getting more efficient. Yes, the cost of accessing the same level of intelligence is decreasing, and hardware is getting better. We're getting more system output throughput

  78. 16:49

    on our-- on the chips. But our view is that demand for compute is gonna continue to increase.

  79. 16:57

    We're gonna see larger models. I mean, DeepSeek, it's over six hundred billion active, uh, sorry, not active, total parameters.

  80. 17:08

    And the demand for more intelligence is insatiable. Reasoning models, as we saw, the Yappi models, they require more compute at inference time. And lastly, agents, whereby twenty, thirty, a hundred plus,

  81. 17:26

    uh, sequential requests to models is not uncommon. These act as multipliers on the demand for compute. And so the house view, playing with these numbers is net net. We're going to continue to see commute-- compute demand increase.

  82. 17:44

    Thanks, everyone. [outro music]