MétaCan
Menu
Back to cohort
Record W2294371741 · doi:10.5555/2886444.2886449

Adoop: MapReduce for ad-hoc cloud computing

2015· article· en· W2294371741 on OpenAlexaff
Mohammad Hamdaqa, Mohamed M. Sabri, Akshay Singh, Ladan Tahvildari

Bibliographic record

VenuePolyPublie (École Polytechnique de Montréal) · 2015
Typearticle
Languageen
FieldComputer Science
TopicCloud Computing and Resource Management
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsComputer scienceCloud computingBig dataProvisioningDistributed computingScheduling (production processes)Programming paradigmAnalyticsImplementationWireless ad hoc networkData scienceComputer networkOperating systemSoftware engineering

Abstract

fetched live from OpenAlex

MapReduce is a widely adopted distributed programming model for big data analytics. It facilitates processing large data sets using a dedicated cloud containing many worker nodes. For most implementations of MapReduce to work, only a few nodes may fail at any given time. This poses a challenge for organizations trying to harness the power of underutilized computing resources by provisioning cloud services on top of existing IT infrastructure. Exploiting ad-hoc clouds for MapReduce operations could yield significant advantages. It could reduce operational costs, improve resource utilization, and enable big data analytics. To the best of our knowledge, only few previous researchers have tried to optimize MapReduce for such volatile, non-dedicated, environments. This paper investigates how Hadoop --the most widely used open-source implementation of MapReduce-- can be optimized to run efficiently in ad-hoc cloud environments, despite the challenges these environments impose. To address these challenges, we present Adoop: a history-based scheduling approach to MapReduce, where the availability history of each node affects Hadoop scheduling decisions. Adoop maintains an availability and utilization based score of all the participating nodes, and dynamically re-adapts task assignments accordingly. A proof-of-concept implementation of Adoop has been provided and made publically available. Our initial experiments show that Adoop outperforms Hadoop in a simulated ad-hoc environment.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.003
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.007
Threshold uncertainty score0.014

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.003
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.002
Science and technology studies0.0020.001
Scholarly communication0.0020.003
Open science0.0040.003
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0040.003

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.019
GPT teacher head0.244
Teacher spread0.225 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designBench or experimental
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations15
Published2015
Admission routes1
Has abstractyes

Explore more

Same venuePolyPublie (École Polytechnique de Montréal)Same topicCloud Computing and Resource ManagementFrench-language works237,207