Clipper: A Low-Latency Online Prediction Serving System
Fields
papers/clipperNotes
Venue verified on the USENIX NSDI '17 program page (session 'Big Data Systems'). Adoption genuinely in-production as a design lineage: Clipper's batch-level front-end/cache abstraction is the direct ancestor of TensorFlow Serving, and NVIDIA cites it as the origin of Triton Inference Server's architecture. IMPORTANT NAMING TRAP: 'Clipper2' is the Triton Inference Server, a different project that reuses the name; do not treat this record as covering Triton — Triton has no peer-reviewed paper, so it is cited via the repository source pap-sys-clipper2-arxiv instead.
VENUE_TRACK BACKFILL 2026-10-04 (paper-fields pass, agent w3p): venue_track 'main'. This is STRUCTURAL rather than researched: nsdi has no Findings volume and no workshop track in which a paper could appear, so 'main' is the only possible honest value and no per-paper evidence was needed. The field is annotated here so that 'findings' and 'workshop' remain MEANINGFUL - a filter for findings=true must return only the papers that actually are findings, which requires every other paper to be explicitly NOT findings.
Cross-references
This record references no other records — it is a leaf. It is cited by 0.