Software and the Concurrency Revolution

598 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Transactional memory (2010, methodology): “However, the software needs to be parallel as well as scalable in order to harvest the multicore performance potential [2, 3, 4].”
Map-Reduce for Machine Learning on Multicore (2006, background): “For multicore systems, Sutter and Larus [25] point out that multicore mostly benefits concurrent applications, meaning ones where there is little communication between cores.”
The problem with threads (2006, background): “Quoting Sutter and Larus again [47]: “The world of client applications is not nearly as well structured and regular.”
Introduction to Embedded Systems - A Cyber-Physical Systems Approach (2013, background): “Threads have a number of difficulties that make it questionable to expose them to programmers as a way to build concurrent programs (Ousterhout, 1996; Sutter and Larus, 2005; Lee, 2006; Hayes, 2007).”
Cyber Physical Systems: Design Challenges (2008, background): “Sutter and Larus [27] observe that " humans are quickly overwhelmed by concurrency and find it much more difficult to reason about concurrent than sequential code.”