MétaCan
Menu
Back to cohort
Record W2049492770 · doi:10.1109/hpcs.2007.23

On the Programming Impact ofMulti-Core,Multi-Processor Nodes inMPI Clusters

2007· article· en· W2049492770 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
fundA Canadian funder is recorded on the work.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicParallel Computing and Optimization Techniques
Canadian institutionsUniversity of Manitoba
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsComputer scienceMulti-core processorParallel computingCore (optical fiber)Cluster (spacecraft)Code (set theory)CacheProcess (computing)Dual (grammatical number)Computer clusterDistributed computingComputer networkOperating systemSet (abstract data type)Telecommunications

Abstract

fetched live from OpenAlex

Increasingly, multi-core processors, multi-processor nodes and multi-core, multi-processor nodes are finding their way into computer clusters. Clusters built using such nodes are already quite common and, inevitably, will become more so over time. As with any new technology, however, the potential benefits are seldom as easy to attain as we expect them to be. In this paper, we explore three fundamental issues related to the use of multi-core, multi-processor nodes in compute clusters using MPI: inter-communication (messaging) efficiency, cache effects (in particular processor affinity) and initial process distribution. Based on some initial experiments using a subset of the NAS parallel benchmarks running on a small scale cluster with dual core, dual processor nodes, we report results on the impact of these issues. From these results we attempt to extrapolate some simple, guidelines that are likely to be generally applicable for optimizing MPI code running on clusters with multi- core, multi-processor nodes.

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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.937
Threshold uncertainty score0.412

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.044
GPT teacher head0.332
Teacher spread0.287 · 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