CS-522: Principles of Computer Systems

A modern computer system spans many layers: applications, libraries, operating systems, networks, and hardware devices. Building a good system entails making the right trade-offs (e.g., between performance, durability, and correctness) and understanding emergent behaviors—the difference between great system designers and average ones is that the really good ones make these trade-offs in a principled fashion, not by trial-and-error. In this course, we identify some of the key principles underlying successful systems, and learn how to solve problems in computing using ideas, techniques, and algorithms from operating systems, networks, databases, programming languages, and computer architecture. The basic courses on these topics teach how the elemental parts of modern systems work; POCS picks up where those courses leave off and focuses on how the pieces come together to form useful, efficient systems.

This course is targeted primarily at students who wish to acquire a deep understanding of computer system design or pursue research in systems. It is an intellectually challenging, fast paced course, in which survival requires a good background in operating systems, databases, networking, programming languages, and computer architecture. Please see the syllabus for more information.

Staff

Instructors

Teaching assistants

We are delighted to have two guest lecturers this semester: Edouard Bugnion and Anne-Marie Kermarrec.

Readings

We use as a textbook Principles of Computer System Design: An Introduction by J. H. Saltzer and M. F. Kaashoek. The linked online book is free for EPFL students. Chapters 7 - 11 are also freely available online as a PDF. You can get the Kindle version or a 20th-century-style paperback for your own library.

Logistics

We hold in-class interactive sessions on Tuesdays 12:15-14:00 and Thursdays 13:15-15:00, both in INM10. Some of these sessions take the form of classic lectures, while others are recitations in which we discuss the week’s readings. The goal of all in-class sessions is to understand in depth the principle(s) of that week, and the connection between it and the concrete instantiations in the assigned readings.

We occasionally assign 1-page writeups called one-pagers (OPs); they are due on Friday night. If, over the weekend, you have new ideas about how to improve your OP, you are welcome to submit an update by Sunday night. However, you must submit a first version by Friday night.

Your grade in the class is broken down approximately as follows: 30% midterm, 40% final, 20% OPs, 10% participation and contribution to the in-class discussions.

POCS is a heavyweight course carrying 7 units of ECTS credit (according to the Conférence universitaire suisse, this means 210 learning hours/semester, i.e., 15 hours/week). This course is meant primarily for students who intend to pursue research in the area of systems, therefore you must have a solid systems background. One way to acquire this background is, for example, by taking at least the following:

Without a solid systems background, it is hard to succeed in POCS. If you wish to brave it out despite an incomplete background, please be ready to spend at least 2x more time than the other students in order to acquire, on the side, the necessary background on your own.

Collaboration policy

We encourage you to discuss the reading materials with your peers, but every assignment you turn in must be your own work. You are not permitted to discuss the topic of the OP with other students prior to your or their final submission. Cheating, plagiarism, and any form of dishonesty will be handled with maximum severity. If you are ever in doubt about whether an action on your part may constitute unacceptable collaboration, please ask the course staff before proceeding—doing so afterward is too late.

Syllabus