Topic

LLM Benchmarking

All digests tagged LLM Benchmarking

Agentic Engineering Benchmarks: How I RANK Astra, Fable 5.1, and Open-Weights thumbnail

· 39:23

Agentic Engineering Benchmarks: How I RANK Astra, Fable 5.1, and Open-Weights

The video argues that relying on generalized AI benchmarks (like the Artificial Analysis Index) is misleading because model performance is a complex, three-dimensional problem involving performance, cost, and speed. The speaker advocates for selecting a curated set of five specialized benchmarks—Terminal-Bench, APEX Agents, AutomationBench, AA-Omniscience, and DeepSWE—to accurately assess model capabilities for specific, real-world agentic engineering tasks, rather than relying on single aggregate scores.

Key takeaways

  1. Model Selection is a 3D Problem 0:40

    Choosing a model requires balancing performance, cost, and speed simultaneously. A model that performs best may be prohibitively expensive or slow, making the trade-off critical for production systems.

  2. Focus on Variance, Not Indices 1:50

    The most valuable benchmarks show significant variance in model performance, indicating 'alpha' or information gain. Flat-lining benchmarks (like some long context retrieval tests) are considered saturated and uninformative.

  3. The Importance of Guardrails (Alignment) 10:30

    AutomationBench is highlighted for its focus on guardrail adherence. A model must not only complete the objective but also avoid triggering guardrail violations, which is crucial for reliable, production-grade agents.

  4. The Value of Honesty (AA-Omniscience) 17:30

    The AA-Omniscience benchmark measures hallucination rate and the cost of honesty. It is critical that an agent can 'opt to not answer' when lacking information, as this prevents cascading errors in long-running agent pipelines.

  5. Long-Horizon Work is Key 27:30

    DeepSWE v1.1 is emphasized for testing long-horizon software engineering tasks. The goal is to build systems that operate autonomously with minimal human oversight, requiring models that maintain consistency over extended periods.

Watch on YouTube Full article

How long can your skills be before your agent forgets what you told it? — Laurie Voss, Arize AI thumbnail

· 22:26

How long can your skills be before your agent forgets what you told it? — Laurie Voss, Arize AI

The capacity of frontier LLMs to follow complex instructions has increased by an estimated tenfold in the last year, moving the instruction ceiling from 200-300 rules to 2,000 to 5,000 rules. This shift fundamentally changes prompt engineering from a 'compression problem' (fitting rules into a small budget) to a 'verification problem' (confirming the model actually obeyed the rules). Developers must now focus on robust output validation (evals) rather than worrying about the length of the skills file.

Key takeaways

  1. Instruction Ceiling Increased by 10x 10:12

    A year ago, models struggled with 200 to 300 instructions. Current frontier models can handle up to 2,000 instructions, with the best models reaching 5,000 rules (6:12).

  2. Failure Mode Shift: From Forgetting to Refusing 20:00

    Models no longer fail by simply forgetting instructions. Failure modes are now diverse: Deepseek V4 Pro forgets; Claude Opus 4.7 refuses at the API level due to safety classifiers; Gemini 3.1 Pro runs out of thinking tokens; and GPT 5.5 writes a partial report and politely states the request is 'stupid' (12:00).

  3. Engineering Focus Shifts to Verification

    The challenge is no longer fitting rules into a small prompt (compression); it is verifying that the model actually followed all instructions, which requires external output checking (an eval) (14:00).

Watch on YouTube Full article

DeepSWE: A Contamination-Resistant Coding Benchmark — James Shi, Datacurve thumbnail

· 17:34

DeepSWE: A Contamination-Resistant Coding Benchmark — James Shi, Datacurve

DeepSWE is a contamination-resistant benchmark featuring 113 original software engineering tasks designed to rigorously test large language model (LLM) capabilities in long-horizon coding problems. Unlike benchmarks that scrape existing pull requests (PRs), DeepSWE's methodology prevents models from cheating via training data leakage. The evaluation focuses on observable behavior and task completion, revealing significant performance gaps between top-tier models and others, particularly concerning the ability to handle multi-part prompts and self-verify code.

Key takeaways

  1. Contamination Resistance 2:03

    DeepSWE utilizes 113 tasks written from scratch, ensuring they were not scraped from existing PRs. This design choice prevents models from cheating by accessing solutions or discussions available in the wild (a major issue with benchmarks like SweetBench Pro) [0:00], [1:03].

  2. Focus on Observable Behavior

    The verifiers are designed to reward correct observable behavior rather than relying on specific, PR-derived implementations or private helper functions. This significantly reduces the risk of false negatives and positives [11:45].

  3. Model Failure Modes Observed 5:20

    Analysis revealed that while stronger models tend to test their own work (a positive sign), they can also exhibit forgetfulness when handling multi-part prompts, such as implementing one required version (e.g., synchronous) but dropping another (e.g., asynchronous) [5:18].

  4. Prompting Style for Realism 10:23

    DeepSWE prompts are designed to be high-level and ambiguous, mirroring real-world engineering tasks, rather than being overly verbose 'to-do lists' that prescribe a specific solution method [10:15].

Watch on YouTube Full article

📅 ThursdAI - LIVE from AI Engineer Worlds Fair - OpenAI, DeepMind, EXO, Sakana & more friends thumbnail

· 2:53:57

📅 ThursdAI - LIVE from AI Engineer Worlds Fair - OpenAI, DeepMind, EXO, Sakana & more friends

This live panel discussion from the AI Engineer World's Fair focuses on the critical shift toward local and open-source AI models. Speakers debated the current state of frontier models (like OpenAI's GPT-5.6) versus decentralized, sovereign AI solutions running on consumer hardware. Key technical topics included model routing (Fugu), agentic workflows using tools like Weights & Biases' Coreweave Ara, and the necessity of local inference to ensure data sovereignty and prevent vendor lock-in.

Key takeaways

  1. The resurgence of Fable 22:40

    Fable is back, marking a significant moment for open models. The discussion highlighted that this trend emphasizes the need for decentralized AI solutions over reliance on single cloud providers.

  2. Local AI and Sovereignty 35:50

    Running large language models (LLMs) locally is presented as crucial for guaranteeing data sovereignty, preventing vendor lock-in, and ensuring continuous operation regardless of cloud provider restrictions.

  3. Model Routing and Orchestration 45:00

    The concept of model routers (like Fugu) was presented as a superior method for achieving high performance, allowing users to dynamically select the best model for specific tasks rather than relying on a single monolithic LLM.

  4. The Agentic Era and Tooling 1:03:20

    Tools like Weights & Biases' Coreweave Ara are emerging to automate the entire AI research loop (auto-research), moving beyond simple chatbots into full agentic co-pilots for ML engineers.

Watch on YouTube Full article