Adoop: MapReduce for ad-hoc cloud computing
Bibliographic record
Abstract
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
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".