atlas

Research map / Large language models / Reasoning and chain of thought

Fast Inference for Augmented Large Language Models

NeurIPS 2025 · Large language models › Reasoning and chain of thought · approach: Efficient LLM serving · 1 citations (OpenAlex)

Read the paperCheck your idea against 108,967 papers

AI-extracted summary. Written by AI from the paper's full text. Numbers and claims can be wrong or missing context, so check the paper before you cite or build on it.

Proposes LAMPS, a scheduler for API-augmented LLM requests that ranks requests by predicted memory-over-time (including API handling strategy: preserve/discard/swap) and adds starvation prevention, implemented on vLLM.

Problem

Size-based and FCFS scheduling perform poorly for API-augmented LLM requests because output length does not reflect total time, and KV-cache memory held during API calls causes head-of-line blocking.

Approach

Predict pre-API output length and API duration, pick the memory handling strategy (preserve, discard-and-recompute, swap) minimizing memory waste before scheduling, then rank requests by their predicted integral of memory over time rather than by length.

Key results

Measured effects reported in the paper

What was changedWhereMeasuredEffect
Integrate request length and API handling strategy into scheduling rather than using FCFSLAMPS on augmented-LLM requests · Multi-API, illustrative exampleaverage request completion time: 11.66 units -> 10 unitsHelped
Use SJF by total length instead of the memory-aware optimized policyAugmented-LLM scheduler · Multi-API, illustrative exampleaverage request completion time: 10 units -> 11 unitsHurt
Add predicted API handling while retaining FCFS scheduling (ablation)vLLM · Multi-API, Vicuna 13Bperformance across reported metricsNo clear effect
Add the LAMPS scheduling policy to predicted API handling (ablation)LAMPS w/o scheduling · Multi-API, Vicuna 13Bperformance across reported metricsHelped
Introduce a starvation-prevention threshold of 100 (ablation)LAMPS scheduler · Multi-API, GPT-J 6Btail latency and throughput: 100Helped
Increase prediction error (ablation)LAMPS predictions · Multi-API, GPT-J 6Bmedian latency: 5%, 10%, 30%, 50%Hurt
Increase prediction error (ablation)LAMPS predictions · Multi-API, GPT-J 6Bthroughput: 5%, 10%, 30%, 50%Hurt
Optimize end-to-end latency rather than prioritizing throughputLAMPS · ToolBenchthroughput vs. INFERCEPTHurt

Surprising findings

Limitations

Experimental setup

Datasets: INFERCEPT dataset ToolBench

Benchmarks: INFERCEPT dataset (single-API, multi-API) ToolBench

Metrics: end-to-end latency time-to-first-token throughput P99 latency Acc-5 Acc-15 MAE

Baselines: vLLM INFERCEPT

Builds on: INFERCEPT vLLM Orca

Closest papers by meaning

Writing a paper in this area? scime draft is a free LaTeX editor with AI included, real-time co-authors and a check of your references and venue rules before you submit. It also imports OpenAI Prism projects.

Open scime draft

Get the next scime Dispatch and a monthly field update

Free. We send a confirmation link first; every email has a one-click unsubscribe. Privacy