Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Colby Ranger

dblp:23/2393 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 2007
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Computer architecture, parallel and distributed computing, and storage systems
1 paper
Parallel and multicore computing · 87% Distributed systems · 6% Hardware reliability and fault tolerance · 6%

Topics — the 6 heaviest of 6, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Parallel and multicore computing › data-parallel programming
mapreduce
0.112007
Evaluating MapReduce for Multi-core and Multiprocessor Systems · HPCA 2007
Parallel and multicore computing
parallel programming models
0.112007
Evaluating MapReduce for Multi-core and Multiprocessor Systems · HPCA 2007
Parallel and multicore computing
parallel programming runtimes
0.112007
Evaluating MapReduce for Multi-core and Multiprocessor Systems · HPCA 2007
Parallel and multicore computing
task scheduling
0.112007
Evaluating MapReduce for Multi-core and Multiprocessor Systems · HPCA 2007
Hardware reliability and fault tolerance
error recovery
0.012007
Evaluating MapReduce for Multi-core and Multiprocessor Systems · HPCA 2007
Distributed systems
fault tolerance
0.012007
Evaluating MapReduce for Multi-core and Multiprocessor Systems · HPCA 2007

Methods — techniques the papers use, named apart from their topics

pthreads · 0.1phoenix runtime · 0.1
YearPublicationVenuePosition
2007 Evaluating MapReduce for Multi-core and Multiprocessor Systems
abstract
This paper evaluates the suitability of the MapReduce model for multi-core and multi-processor systems. MapReduce was created by Google for application development on data-centers with thousands of servers. It allows programmers to write functional-style code that is automatically parallelized and scheduled in a distributed system. We describe Phoenix, an implementation of MapReduce for shared-memory systems that includes a programming API and an efficient runtime system. The Phoenix runtime automatically manages thread creation, dynamic task scheduling, data partitioning, and fault tolerance across processor nodes. We study Phoenix with multi-core and symmetric multiprocessor systems and evaluate its performance potential and error recovery features. We also compare MapReduce code to code written in lower-level APIs such as P-threads. Overall, we establish that, given a careful implementation, MapReduce is a promising model for scalable performance on shared-memory systems with simple parallel code
Colby Ranger, Ramanan Raghuraman, Arun Penmetsa, Gary R. Bradski, Christoforos E. Kozyrakis
HPCA1