- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper focuses on multi-tenant serving for Flow-based VLA models. Treating complete trajectories as indivisible units limits batching efficiency across requests with differing step counts, while per-step continuous batching incurs prohibitive kernel launch and scheduling overheads. The paper propose RONDO, a framework that serves heterogeneous Flow-VLA requests through resumable execution, segmentation at the earliest request completion, and dynamic remaining-work bucketing. Experiments with π0.5 on eight Ascend 910C NPUs show substantial latency reductions and improved task success in wall-clock LIBERO simulations.
Critical strengths
- The execution abstraction explicitly preserves each request's integration grid, progress, latent state, and conditioning cache, providing a concrete design for heterogeneous VLA batching.
- The combination of completion boundaries and load-dependent bucketing addresses a meaningful trade-off between batch occupancy and scheduling overhead.
Critical weaknesses
- The contribution of completion-boundary scheduling is not isolated. TetriServe (ASPLOS 2026) uses multistep scheduling and compares 1-, 5-, and 10-step granularities. Therefore, a fixed-multistep baseline using the same execution engine is important. Existing bucketing ablations cannot determine whether the gains come from the specific completion rule or simply from less frequent scheduling. A matched overhead breakdown would also help establish how much of Iter-CB's slowdown is intrinsic and how much is implementation-dependent.
- The overall evaluation is somewhat limited; it would be better to include other flow-based VLA/WAM methods, such as Lingbot-VA, Lingbot-VLA, and Fast-WAM.
Questions for authors
Please refer to the weaknesses.
Dear Reviewers,
The authors have submitted their rebuttal. Please review it and share your comments. If anything is unclear or requires clarification, please let the authors know as soon as possible. The author–reviewer discussion period ends on 18 November.
Best regards,
AC