papers-we-love / portland

Papers We :heart: Portland

Papers We Love Portland

This is the repository for the Portland, OR chapter of Papers We Love. As a local chapter we follow the Papers We Love Code of Conduct.

Welcome

What was the last paper you read and loved within the realm of computing? What did it inspire you to build or tinker with? Come share the ideas in an awesome academic/research paper with fellow engineers, programmers, and paper-readers. Lead a session and show off code that you wrote that implements these ideas or just give us the lowdown about the paper. Or, just come, listen, and discuss!

We're curating this repository for papers presented at PWL PDX. You can contribute by adding PR's for papers, code, and/or links to other repositories, like the main Papers We Love repo, here.

If you need to reach out to us or have ideas for papers, please join the Meetup group below and post a message.

Information

Events are posted to the Papers We Love PDX Meetup.

There is also a Discord channel: https://discord.gg/ZHqZ2W9QQt

Contact

• Dave Peticolas | GitHub | Web | Email
• Chris Mason | GitHub | Email

History

This chapter was formerly run by:

• Carl Lerche | GitHub
• Katherine "kf" Fellows | GitHub
• Nick Fitzgerald | GitHub

portland's Issues

[Paper Suggestion] Lightweight Preemptible Functions

Paper Suggestion

• Title: Lightweight Preemptible Functions
• Link: https://www.usenix.org/conference/atc20/presentation/boucher

Content Summary

Lamenting the lack of a natural userland abstraction for preemptive interruption and asynchronous cancellation, we propose lightweight preemptible functions, a mechanism for synchronously performing a function call with a precise timeout that is lightweight, efficient, and composable, all while being portable between programming languages. We present the design of libinger, a library that provides this abstraction, on top of which we build libturquoise, arguably the first general-purpose and backwards-compatible preemptive thread library implemented entirely in userland. Finally, we demonstrate this software stack’s applicability to and performance on the problems of combatting head-of-line blocking and time-based DoS attacks.

[Paper Suggestion]: C-Store

Paper Suggestion

• Title: C-Store: A Column-oriented DBMS
• Link: https://web.stanford.edu/class/cs345d-01/rl/cstore.pdf

Content Summary

This paper presents the design of a read-optimized relational DBMS that contrasts sharply with most current systems, which are write-optimized. Among the many differences in its design are: storage of data by column rather than by row, careful coding and packing of objects into storage including main memory during query processing, storing an overlapping collection of column-oriented projections, rather than the current fare of tables and indexes, a non-traditional implementation of transactions which includes high availability and snapshot isolation for read-only transactions, and the extensive use of bitmap indexes to complement B-tree structures.

[Paper Suggestion] Attention is all you need

Paper Suggestion

• Title: Attention is all you need
• Link: https://arxiv.org/abs/1706.03762

Content Summary

The dominant sequence transduction models are based on complex recurrent or convolutional neural networks in an encoder-decoder configuration. The best performing models also connect the encoder and decoder through an attention mechanism. We propose a new simple network architecture, the Transformer, based solely on attention mechanisms, dispensing with recurrence and convolutions entirely. Experiments on two machine translation tasks show these models to be superior in quality while being more parallelizable and requiring significantly less time to train. Our model achieves 28.4 BLEU on the WMT 2014 English-to-German translation task, improving over the existing best results, including ensembles by over 2 BLEU. On the WMT 2014 English-to-French translation task, our model establishes a new single-model state-of-the-art BLEU score of 41.8 after training for 3.5 days on eight GPUs, a small fraction of the training costs of the best models from the literature. We show that the Transformer generalizes well to other tasks by applying it successfully to English constituency parsing both with large and limited training data.

[Paper Suggestion] Foundational distributed systems papers

This is a collection of distributed system papers we could choose from:

https://muratbuffalo.blogspot.com/2021/02/foundational-distributed-systems-papers.html

[Paper Suggestion] A Certain Tendency Of The Database Community

Paper Suggestion

• Title: A Certain Tendency Of The Database Community
• Link: https://arxiv.org/abs/1510.08473

Content Summary

We posit that striving for distributed systems that provide "single system image" semantics is fundamentally flawed and at odds with how systems operate in the physical world. We realize the database as an optimization of this system: a required, essential optimization in practice that facilitates central data placement and ease of access to participants in a system. We motivate a new model of computation that is designed to address the problems of computation over "eventually consistent" information in a large-scale distributed system.

[Paper Suggestion]: Keeping CALM: When Distributed Consistency is Easy

Paper Suggestion

• Title: Keeping CALM: When Distributed Consistency Is Easy
• Link: https://cacm.acm.org/magazines/2020/9/246941-keeping-calm/fulltext

Content Summary

Distributed systems are tricky. Multiple unreliable machines are running in parallel, sending messages to each other across network links with arbitrary delays. How can we be confident these systems do what we want despite this chaos?

[Paper Suggestion] Why Logical Clocks are Easy

Paper Suggestion

• Title: Why Logical Clocks are Easy
• Link: https://queue.acm.org/detail.cfm?id=2917756

Content Summary

Overview of logical clocks that is congruent with a lot of our recent discussions.

[Paper Suggestion] Calvin: Fast Distributed Transactions for Partitioned Database Systems

Paper Suggestion

• Title: Calvin: Fast Distributed Transactions for Partitioned Database Systems
• Link: https://cs.yale.edu/homes/thomson/publications/calvin-sigmod12.pdf

Content Summary

Splits the ordering of transactions from their execution to improve distributed transaction performance.

Replace logo used on your Twitter account

Please use this logo on @pwlpdx

[Paper Suggestion] Capability Myths Demolished

Paper Suggestion

• Title: Capability Myths Demolished
• Link: https://srl.cs.jhu.edu/pubs/SRL2003-02.pdf

Content Summary

We address three common misconceptions about capability-based systems: the Equivalence Myth (access control list systems and capability systems are formally equivalent), the Confinement Myth (capability systems cannot enforce confinement), and the Irrevocability Myth (capability-based access cannot be revoked). The Equivalence Myth obscures the benefits of capabilities as compared to access control lists, while the Confinement Myth and the Irrevocability Myth lead people to see problems with capabilities that do not actually exist.

The prevalence of these myths is due to differing interpretations of the capability security model. To clear up
the confusion, we examine three different models that have been used to describe capabilities, and define a set of seven security properties that capture the distinctions among them. Our analysis in terms of these properties shows that pure capability systems have significant advantages over access control list systems: capabilities provide much better support for least-privilege operation and for avoiding confused deputy problems.

[Paper Suggestion] Spanner

Paper Suggestion

• Title: Spanner: Google's Globally-Distributed Database
• Link: https://static.googleusercontent.com/media/research.google.com/en//archive/spanner-osdi2012.pdf

Content Summary

Spanner is Google’s scalable, multi-version, globally-distributed, and synchronously-replicated database. It is the first system to distribute data at global scale and support externally-consistent distributed transactions. This paper describes how Spanner is structured, its feature set, the rationale underlying various design decisions, and a novel time API that exposes clock uncertainty. This API and its implementation are critical to supporting external consistency and a variety of powerful features: non-blocking reads in the past, lock-free read-only transactions, and atomic schema changes, across all of Spanner.

[Paper Suggestion] NDN

Paper Suggestion

• Title: Named Data Networking
• Link: https://dl.acm.org/doi/pdf/10.1145/2656877.2656887
• Link: https://named-data.net/publications/named_data_networking_ccr/
• Code: https://github.com/named-data/mini-ndn
• Video: https://youtu.be/48VUoBh8gMM

Content Summary

Named Data Networking (NDN) is one of five projects funded by the U.S. National Science Foundation under its Future
Internet Architecture Program. NDN has its roots in an earlier project, Content-Centric Networking (CCN), which
Van Jacobson first publicly presented in 2006. The NDN project investigates Jacobson’s proposed evolution from to-
day’s host-centric network architecture (IP) to a data-centric network architecture (NDN). This conceptually simple shift
has far-reaching implications for how we design, develop, deploy, and use networks and applications. We describe the
motivation and vision of this new architecture, and its basic components and operations. We also provide a snapshot of
its current design, development status, and research challenges. More information about the project, including pro-
totype implementations, publications, and annual reports, is available on named-data.net.

[Paper Suggestion] DevEx: What Actually Drives Productivity

Paper Suggestion

• Title: DevEx: What Actually Drives Productivity
• Link: https://queue.acm.org/detail.cfm?id=3595878

Content Summary

Engineering leaders have long sought to improve the productivity of their developers, but knowing how to measure or even define developer productivity has remained elusive. Past approaches, such as measuring the output of developers or the time it takes them to complete tasks, have failed to account for the complex and diverse activities that developers perform. Thus, the question remains: What should leaders measure and focus on to improve developer productivity?

Additional Papers We Love assets

@carllerche attached are some additional Papers We Love assets for the Portland chapter for use on accounts such as twitter, etc.

https://www.dropbox.com/s/aueiowakdm7eztu/pwl-pdx.zip?dl=0

Thanks!