PapersSelected73°

PACE framework for dialogue serving

PACE: Perceived-Latency-Aware Cascading Service Routing and Filler Control for QoE-Efficient Retrieval-Augmented Dialogue Serving

Why we picked it

PACE reduces response time by 2.4 times compared to RAG at high load, making it valuable for real-time dialogue systems in customer service.

PACE is a retrieval-augmented dialogue serving framework that minimizes Perceived Time-to-First-Response (PTFR) under quality/cost constraints. On 75k CarQA requests, PACE halves pure-LLM PTFR at P95 (0.29s vs 0.53s). The adaptive controller outperforms RAG by 2.4 times at high load with equal quality. The filler controller cuts calls by 94% with zero conflict.

Original · arXiv cs.AI

PACE: Perceived-Latency-Aware Cascading Service Routing and Filler Control for QoE-Efficient Retrieval-Augmented Dialogue Serving

We present the PACE, a framework for retrieval-augmented dialogue serving that formalizes Perceived Time-to-First-Response (PTFR) as a QoE objective and minimizes it under quality/cost constraints. Unlike prior work on cascaded routing, semantic caching, or adaptive retrieval, PACE jointly controls which answer source composes the response and what fills the waiting window. Deployed on a humanoid-robot sales service, it combines three mechanisms: a load-adaptive cascading router, a joint path-filler controller, and volatility-aware cache admission. On 75k CarQA requests, the cascade halves pure-LLM PTFR at P95 (0.29 vs 0.53s at c16). The adaptive controller reaches 0.41s P95, outperforming RAG by 2.4 times at high load with equal quality. The filler controller cuts calls by 94% with zero conflict. Volatility-aware admission reduces stale answers from 86% to 0%. A gating rule ensures the controller never worse than the baseline, with exposure bounded by one hold period. This is the first quantification of filler-answer conflict risk in deployed services.