The TWIML AI Podcast
The TWIML AI Podcast

Infrastructure Scaling and Compound AI Systems with Jared Quincy Davis - #740

In this episode, Jared Quincy Davis, founder and CEO at Foundry, introduces the concept of "compound AI systems," which allows users to create powerful, efficient applications by composing multiple, often diverse, AI models and services. We discuss how these "networks of networks"

Featured Speakers

Jared Quincy Davis Guest

Topics Discussed

Episode Summary

Executive Summary: The episode argues that AI’s next leap will come less from a single frontier model and more from “compound AI systems” that combine multiple models, verifiers, routers, and scheduling policies. Jared Quincy Davis explains how ensembles, best-of-N search, distillation, and inference-time parallelism can improve accuracy, latency, and cost simultaneously—especially on verifiable tasks like code and math—while also creating new infra and cloud design opportunities.

Main Topics: Compound AI systems as a new design paradigm (Priority: 5/5): Davis defines compound systems as architectures that compose multiple model calls, verifiers, and selection policies rather than relying on a single monolithic model. He frames this as a frontier-pushing direction for both research and infrastructure. Best-of-N, ensembles, and verifier-based selection (Priority: 5/5): The conversation centers on simple but powerful inference-time techniques: running many replicas, early stopping, majority vote, and verifier/judge layers. These methods can improve quality and sometimes lower cost on verifiable tasks. Verifiable tasks and frontier gains (Priority: 4/5): Davis emphasizes that tasks like code generation, math, and proofs are ideal for compound methods because correctness is easier to check than generate. He cites strong gains on hard benchmarks and notes that gains can be amplified when verification is reliable. Economics of inference and model dispersion (Priority: 5/5): The episode highlights rapidly falling inference costs and large price/performance gaps across providers and model families. This dispersion creates opportunities for routing, mixing models, and exploiting cheaper systems without sacrificing quality. Systems co-design and infrastructure implications (Priority: 5/5): Davis argues that model architecture, training, and cloud infrastructure must be designed together. He contrasts vertical scaling (longer reasoning, more memory, tightly coupled hardware) with horizontal scaling (many independent replicas) and says each needs different scheduling and pricing. Emerging toolkits and research frameworks (Priority: 4/5): The discussion covers Boundary/Foundry’s Ember framework and related papers such as Networks of Networks and LLM Selector. These tools aim to make compound architectures easy to express, search, and deploy, similar to how PyTorch enabled neural networks. Foundry’s business thesis on AI cloud scheduling (Priority: 4/5): Davis explains Foundry’s goal of improving the economics of AI infrastructure by matching workloads to the right compute regime—batch, preemptible, distributed, or low-latency—thereby creating surplus for both users and providers.

Key Arguments: Longer reasoning traces can be worse on average for some reasoning models; parallel replicas with early stopping can outperform single calls in speed, accuracy, and sometimes cost. On highly verifiable tasks, compound systems can push the performance frontier dramatically; Davis says Networks of Networks showed 9%+ gains on difficult benchmarks. A verifier-based judge can be much cheaper than a full generative judge because it only needs to certify correctness with thumbs-up/thumbs-down outputs. Model diversity matters: combining different models across steps of a pipeline can beat using the single best monolithic model across all steps. Inference costs are falling rapidly, making large-scale parallel inference and novel architectures increasingly practical. The future of AI will likely involve specialized niches—some workloads needing tightly coupled hardware and others benefiting from massively distributed replicas. Infrastructure constraints shape research direction; better scheduling, batching, and virtualization will unlock new algorithmic ideas. Distillation, speculative decoding, and MoE-like patterns are early examples of compound systems already embedded in mainstream AI. Foundry’s cloud thesis is that compute should be priced and scheduled according to workload flexibility, enabling cheaper batch work and better utilization overall.

Data Points: Inference cost decline: ~10x per year for the last 3 years - Davis describes rapidly falling inference costs as a key reason compound architectures are becoming viable. Cost reduction potential: 1000x - He says that getting GPT-4-level performance has become dramatically cheaper over time, with roughly 1000x improvement at a baseline performance level. Benchmark gains: 9%+ - He cites the Networks of Networks paper showing large gains on hard, highly verifiable benchmarks where prior generation-over-generation improvements were around 1%. Cost dispersion between models: $150 per million tokens vs. $0.03 per million tokens - He compares O1 Pro pricing to DeepSeek R1 to illustrate how extreme the price gap can be across models. Observed cost savings: 12–20x - Davis says Foundry has helped some workloads cut inference costs by this amount, especially preemptible, checkpointable, or batch-friendly jobs. Gains on cost frontier: Over 1000x - He says simple composition and routing methods have produced more than 1000x cost gains in some settings while preserving performance. Replica count example: 10 replicas - He repeatedly describes best-of-N and early-stopping setups using around 10 parallel copies of a reasoning model. Large-scale search example: 1 million replicas - He cites AlphaCode-style horizontal scaling as an extreme example of many parallel candidate generations. Workload timing example: 6 hours within the next 12 hours - Used to describe batch-friendly compute that can be scheduled flexibly without strict start-time requirements. Infrastructure benchmark analogy: NVL72 - He references NVIDIA’s large interconnected system as an example of hardware suited to vertical inference-time scaling.

Pivotal Quotes: "all other things being equal, the longer that they think for a given problem, the more likely it is that they're going to get the answer wrong" — Jared Quincy Davis: Introduced as the core intuition behind why simple parallelism and early stopping can outperform longer single reasoning traces. "you can actually push the frontier almost arbitrarily far on tasks that are highly verifiable" — Jared Quincy Davis: Explaining the theoretical upside of best-of-N and verifier-based compound systems for code, math, and proof-like tasks. "I think we're in those very, very early days still" — Jared Quincy Davis: Describing the state of compound AI architecture research and arguing there is still substantial room for new methods and tools.

Implications: AI systems will likely become modular, routed, and workload-aware. For practitioners, simple ensembles and verifiers are an immediate win; for the industry, the bigger shift is toward specialized infra that schedules inference like a heterogeneous cloud utility.

🔓 Sign Up for Unlimited Episode Search

About The TWIML AI Podcast

View all episodes from The TWIML AI Podcast