Skip to content

Orchestra-Research/AI-Research-SKILLs / 20-ml-paper-writing/systems-paper-writing

systems-paper-writing

Verified

Comprehensive guide for writing systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Provides paragraph-level structural blueprints, writing patterns, venue-specific checklists, reviewer guidelines, LaTeX templates, and conference deadlines. Use this skill for all systems conference paper writing.

templates/osdi2026/references.bib

View on GitHub
% OSDI 2026 Example Bibliography
%
% This file contains example references demonstrating different BibTeX entry
% types commonly used in systems papers. Replace with your actual references.
%
% Entry types demonstrated:
%   inproceedings  -- Conference paper (most common in systems)
%   article        -- Journal article
%   techreport     -- Technical report
%   phdthesis      -- Doctoral dissertation
%   misc           -- ArXiv preprint, website, or software
%   book           -- Book reference

%----------------------------------------------------------------------
% Conference papers (inproceedings) -- most common in systems
%----------------------------------------------------------------------

@inproceedings{dean2004mapreduce,
  author    = {Dean, Jeffrey and Ghemawat, Sanjay},
  title     = {{MapReduce}: Simplified Data Processing on Large Clusters},
  booktitle = {Proceedings of the 6th USENIX Symposium on Operating Systems
               Design and Implementation (OSDI)},
  year      = {2004},
  pages     = {137--150},
  address   = {San Francisco, CA},
  publisher = {USENIX Association},
}

@inproceedings{abadi2016tensorflow,
  author    = {Abadi, Mart\'{\i}n and Barham, Paul and Chen, Jianmin and
               Chen, Zhifeng and Davis, Andy and Dean, Jeffrey and
               Devin, Matthieu and Ghemawat, Sanjay and Irving, Geoffrey and
               Isard, Michael and others},
  title     = {{TensorFlow}: A System for Large-Scale Machine Learning},
  booktitle = {Proceedings of the 12th USENIX Symposium on Operating Systems
               Design and Implementation (OSDI)},
  year      = {2016},
  pages     = {265--283},
  address   = {Savannah, GA},
  publisher = {USENIX Association},
}

@inproceedings{moritz2018ray,
  author    = {Moritz, Philipp and Nishihara, Robert and Wang, Stephanie and
               Tumanov, Alexey and Liaw, Richard and Liang, Eric and
               Elibol, Melih and Yang, Zongheng and Paul, William and
               Jordan, Michael I. and Stoica, Ion},
  title     = {{Ray}: A Distributed Framework for Emerging {AI} Applications},
  booktitle = {Proceedings of the 13th USENIX Symposium on Operating Systems
               Design and Implementation (OSDI)},
  year      = {2018},
  pages     = {561--577},
  address   = {Carlsbad, CA},
  publisher = {USENIX Association},
}

@inproceedings{zaharia2012spark,
  author    = {Zaharia, Matei and Chowdhury, Mosharaf and Das, Tathagata and
               Dave, Ankur and Ma, Justin and McCauley, Murphy and
               Franklin, Michael J. and Shenker, Scott and Stoica, Ion},
  title     = {Resilient Distributed Datasets: A Fault-Tolerant Abstraction
               for In-Memory Cluster Computing},
  booktitle = {Proceedings of the 9th USENIX Symposium on Networked Systems
               Design and Implementation (NSDI)},
  year      = {2012},
  pages     = {15--28},
  address   = {San Jose, CA},
  publisher = {USENIX Association},
}

@inproceedings{ongaro2014raft,
  author    = {Ongaro, Diego and Ousterhout, John},
  title     = {In Search of an Understandable Consensus Algorithm},
  booktitle = {Proceedings of the 2014 USENIX Annual Technical Conference
               (USENIX ATC)},
  year      = {2014},
  pages     = {305--319},
  address   = {Philadelphia, PA},
  publisher = {USENIX Association},
}

@inproceedings{verma2015borg,
  author    = {Verma, Abhishek and Pedrosa, Luis and Korupolu, Madhukar and
               Oppenheimer, David and Tune, Eric and Wilkes, John},
  title     = {Large-Scale Cluster Management at {Google} with {Borg}},
  booktitle = {Proceedings of the 10th European Conference on Computer
               Systems (EuroSys)},
  year      = {2015},
  pages     = {1--17},
  address   = {Bordeaux, France},
  publisher = {ACM},
}

%----------------------------------------------------------------------
% Journal article (article)
%----------------------------------------------------------------------

@article{lamport1978time,
  author    = {Lamport, Leslie},
  title     = {Time, Clocks, and the Ordering of Events in a Distributed System},
  journal   = {Communications of the ACM},
  volume    = {21},
  number    = {7},
  pages     = {558--565},
  year      = {1978},
  doi       = {10.1145/359545.359563},
  publisher = {ACM},
}

%----------------------------------------------------------------------
% Technical report (techreport)
%----------------------------------------------------------------------

@techreport{lamport2001paxos,
  author      = {Lamport, Leslie},
  title       = {Paxos Made Simple},
  institution = {Microsoft Research},
  year        = {2001},
  number      = {MSR-TR-2001-33},
  address     = {Redmond, WA},
}

%----------------------------------------------------------------------
% ArXiv preprint (misc)
%----------------------------------------------------------------------

@misc{kwon2023vllm,
  author        = {Kwon, Woosuk and Li, Zhuohan and Zhuang, Siyuan and
                   Sheng, Ying and Zheng, Lianmin and Yu, Cody Hao and
                   Gonzalez, Joseph E. and Zhang, Hao and Stoica, Ion},
  title         = {Efficient Memory Management for Large Language Model Serving
                   with {PagedAttention}},
  year          = {2023},
  eprint        = {2309.06180},
  archivePrefix = {arXiv},
  primaryClass  = {cs.OS},
}

%----------------------------------------------------------------------
% PhD thesis (phdthesis)
%----------------------------------------------------------------------

@phdthesis{zaharia2014thesis,
  author  = {Zaharia, Matei},
  title   = {An Architecture for Fast and General Data Processing on
             Large Clusters},
  school  = {University of California, Berkeley},
  year    = {2014},
  address = {Berkeley, CA},
}
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall