Each student will be assigned one paper to present in a 70-80 minute talk. When you present a paper, you are expected to fully understand it (including material not covered by your slides), be familiar with previous work, and be able to compare the paper with relevant related work.
The goal of your presentation is to make sure we understand the paper too, and to facilitate discussion:Most papers have the authors' slides on the web, and a video of the presentation given at the conference is also often available. You may freely use these materials when preparing your presentation, but keep in mind that conference talks are different from your talk in many ways:
Feel free to discuss your presentation with me before you give it.
To encourage discussion, every student (except the speaker) should email me a short review of the paper discussed in the meeting within one week after the meeting.
The report should be up to one page and should be organized as follows:
Here are a couple of resources on how to read and evaluate research papers:
Date | Speaker | Paper |
---|---|---|
Nov 2 | Adam Morrison |
Introduction and logistics |
Nov 9 | No meeting |
|
Nov 16 | No meeting |
|
Nov 23 | Adam Morrison |
Background: distributed transactions |
Nov 30 | No meeting |
|
Dec 7 | Alon Resler |
Extracting More Concurrency from Distributed Transactions (OSDI'14) |
Dec 14 | Adam Morrison |
Background: big data systems |
Dec 21 | Adi Gilboa |
Discretized Streams: Fault-Tolerant Streaming Computation at Scale (SOSP'13) |
Dec 28 | Eyal Agiv |
Latency-Tolerant Software Distributed Shared Memory (USENIX ATC'16 best paper) |
Jan 4 | Adam Morrison |
Background: multi-core |
Jan 11 | Nir David |
Algorithmic Improvements for Fast Concurrent Cuckoo Hashing (EuroSys'14) |