The Harvard Systems Group at the John A. Paulson School of Engineering and Applied Sciences (SEAS) operates at the vital intersection of systems, theory, and hardware. We design and build the architectures, networks, and databases that form the backbone of modern computing.
From scaling global cloud infrastructure to optimizing the software-hardware interface, we don’t just study systems—we reinvent the layers that power the future.
Saurabh will examine both sides of AI’s effect on the reliability and security of computing systems—a foe when it complicates reasoning about probabilistic programs and enables phishing at scale, a friend when it powers causal root-cause diagnosis and automatic vulnerability patching—and highlight recent work from the NSF Center Chorus on streaming ML with probabilistic accuracy guarantees and secure decentralized ML.
eventlocation_onSEC 2.122 & 2.123personMinghao Li (Harvard University)
As ML training scales across racks, data-center buildings, regions, and even federated clients, periodic synchronization leaves compute idle and prolongs iterations. Minghao will argue for network-aware co-design—jointly optimizing algorithms, parallelism and pipeline strategies, and heterogeneity handling—and present THC, ScaleAcross Explorer, and FIELDING as works that cut synchronization costs across increasingly large deployments.
Many workloads, such as repeated scans and LSM-tree compaction, access groups of objects in similar orders, forming access loops that several cache eviction algorithms handle well—though it remains unclear what makes them effective. Yunjia will distill the structural features behind this efficiency into portable eviction gadgets that can be plugged into existing policies, and show that these features also improve cache stability by reducing miss-ratio anomalies and cliffs.
Cache eviction is usually presented as a ranking problem. LRU ranks objects by
recency. LFU ranks them by frequency. More advanced algorithms combine several
signals, adapt their parameters, and maintain increasingly sophisticated data
structures to decide which object is least valuable.
Most LLM servers treat a deployed model as fixed: its weights have one
precision, its KV cache has one memory budget, and both remain unchanged until
the process restarts.