GrabDaniel TaiProblem & solution
Modernising Grab’s model serving platform with NVIDIA Triton Inference Server
Summary
Catwalk, Grab’s machine learning model serving platform, accumulated technical debt by maintaining separate inference engines for ONNX, PyTorch, TensorFlow, and vLLM, contributing to higher latency, lower throughput, and rising costs. The team evaluated NVIDIA Triton Inference Server and began consolidating those engines around it, initially adopting ONNX. The Triton manager combines a server manager, which retrieves and verifies models, prepares configurations, launches Triton, and monitors health, with a proxy that translates legacy API requests without requiring client code changes. Benchmarks showed at least five times the traffic capacity for a transformer model; rollout reached over 50% of online deployments in 10 days, while some larger models saw p90 latency fall from 120 ms to 20 ms.
Context
Catwalk’s support for multiple inference frameworks required maintaining various inference engines, preserving backward compatibility, and managing deprecated components such as the ONNX server. The resulting technical debt degraded performance through increased latency, reduced throughput, and escalating costs, making larger models difficult to serve efficiently or cost-effectively.
Approach / What changed
The team evaluated NVIDIA Triton Inference Server and is consolidating Catwalk’s inference engines into a unified Triton engine, beginning with ONNX. The Triton manager integrates Triton through a server manager that handles model retrieval, verification, configuration, launch, and health monitoring, plus a proxy that translates legacy API requests and preserves compatibility without requiring user code changes.
Takeaways
Triton handled at least 5 times the traffic of Catwalk’s existing ONNX server for a transformer-based model while maintaining excellent latency; batching provided additional performance improvements.
More than 50% of online model deployments migrated within 10 days, with backward-compatibility testing allowing most users to remain unaware of the transition.
Across 11 migrated production ML services, average infrastructure spend fell by approximately 20% over the 14 days after cut-over, while some individual models achieved over 90% cost reductions.
Source and freshness
- Source
- engineering.grab.com
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.