Replacing Large Language Models with Jev Decision Models for Low-Latency Edge Service Orchestration
Delong Li, Xu Wang, Haochen Gong, Rui Lang, Guangsheng Yu
University of Technology Sydney
Published September 26, 2026 · on the feed October 2, 2026 · ▲ 5 · arXiv 2609.22753
The abstract
Natural-language service requests can require a language-model decision before execution starts, consuming part of the request's latency budget. We integrate Jev's decision-oriented application programming interface (API) into edge service orchestration to reduce this overhead while retaining service completion. The integration extracts four to eight bounded intent fields and applies a shared validator, admission policy, and scheduler, accounting for decision waiting throughout the request timeline. We compare Jev, two self-hosted decision models, and three hosted large language models (LLMs) on 8,280 verified requests and on a live admission path with modeled execution and a real optical character recognition service. Across 33 test conditions, Jev reduces median decision latency by 22.7-64.5% relative to the fastest LLM. This latency barely moves with input size, contract width, or catalog size. On four-field contracts, Jev's API fees per correct decision are 59.7-80.9% lower at a cost of a few exact-match points, while wide contracts mark the limit of the substitution. Receiving the service catalog with each request, Jev names unseen services as accurately as known ones. On the live admission path, Jev keeps 0.91-0.95 of requests exact and on time at loads where the LLMs fall below 0.1. Since caching repeated descriptions gives the interpreters nearly the same latency, Jev's gain lies in fresh decisions. These results support decision-model substitution for latency-bound admission on bounded contracts.
The Brief
2:38A short podcast summary of the paper. Written and voiced by AI.
Transcript
Replacing Large Language Models with Jev Decision Models for Low-Latency Edge Service Orchestration. By Delong Li and four others, from the University of Technology Sydney. Published on the twenty-sixth of September. Its code repository is worked out: about ninety-five source files, with a readme and a licence.
When a service request arrives in natural language, a language model may have to make a decision before anything is executed, and that decision eats into the request's latency budget. The claim here is that a decision model can take that job over. The authors integrate Jev's decision-oriented application programming interface into edge service orchestration, aiming to cut the overhead while still completing the service. The integration pulls out four to eight bounded intent fields from each request, then passes them through a shared validator, admission policy and scheduler, with decision waiting accounted for across the whole timeline of the request.
The comparison sets Jev against two self-hosted decision models and three hosted large language models. It runs on eight thousand two hundred and eighty verified requests, and on a live admission path that combines modeled execution with a real optical character recognition service.
Across thirty-three test conditions, Jev cuts median decision latency by between twenty-two point seven and sixty-four point five percent relative to the fastest LLM. That latency barely moves as input size, contract width or catalog size grow. On four-field contracts, the API fees per correct decision come in fifty-nine point seven to eighty point nine percent lower, paid for with a few exact-match points. Given the service catalog alongside each request, Jev names unseen services as accurately as known ones. And on the live admission path, it keeps between zero point nine one and zero point nine five of requests exact and on time, at loads where the LLMs fall below zero point one.
The limits are drawn clearly. Wide contracts mark where the substitution stops working, so the result is about bounded contracts, the narrow forms with a handful of fields. There is a second qualification. Caching repeated descriptions gives the language-model interpreters nearly the same latency as Jev, which means the advantage lives in fresh decisions, not in requests that have been seen before. And the cost saving is measured against a small loss in exact-match accuracy, not for free.
Put those together and the conclusion is specific rather than sweeping. For admission decisions bound by latency, on contracts with a bounded set of fields, swapping the language model for a decision model buys speed that holds steady under load, at a modest price in exactness. Outside those conditions, on wide contracts or cached requests, the case for the swap weakens or disappears.
Paper Quest · 7 chapters · about 41 min
Play this paper
Learn it by doing: make the calls the authors made, guess the result before you see it, and defend it in a viva graded on your own words. Chapter 1 is right here.
Chapter 1 🧩 · The problem
Every millisecond spent deciding is a millisecond the job doesn't get.
You run edge services that take requests in plain language, such as reading the text in an image and returning it before a deadline.
The road ahead
- 1 · The problem ~7 min When a language model must read every plain-language request before work starts, its waiting time eats into the deadline the job itself needs.
- 2 · What came before ~3 min
- 3 · The key idea ~9 min Swap the text-writing interpreter for a decision model that just picks a few bounded field values, and keep everything downstream the same.
- 4 · Choose your own research ~3 min
- 5 · Build the method ~8 min Each request is turned into a few bounded fields, checked, admitted against deadline and capacity, then scheduled onto the edge node that can finish it soonest.
- 6 · The experiment ~6 min You’ll guess: At loads where Jev keeps most live requests exact and on time, how did the hosted LLMs fare?
- 7 · The viva ~5 min Three questions from the examiners, answered in your own words. Win it for the paper’s trophy.
Free, with Google or an email address. Your stars and progress are kept.