MétaCan
Menu
Back to cohort
Record W4312638836 · doi:10.1109/ic2e55432.2022.00039

Poster Paper: Operating System Support for Applications Performance Analysis

2022· article· en· W4312638836 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.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware System Performance and Reliability
Canadian institutionsBrock University
Fundersnot available
KeywordsComputer scienceCode refactoringTracingCloud computingDistributed computingOpen sourceSoftware engineeringMulti-core processorOperating systemSoftware

Abstract

fetched live from OpenAlex

In order to classify common performance issues of multi-core applications, used in cloud computing and distributed systems, and offer solutions to them, performance antipatterns have been introduced by researchers. Performance antipatterns help developers refactor inefficient code, and are exceptionally useful for multi-threaded applications, where problems can be difficult to diagnose. However, existing performance antipattern detection methods do not properly examine operating system-wide resources, leading to imprecise metrics and results. In this paper, a novel system-level execution tracing method is presented for detecting the One Lane Bridge performance antipattern. This method is validated through a case study performed on an open-source multi-threaded application, where we diagnosed performance issues.

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: Empirical · Consensus signal: none
Teacher disagreement score0.917
Threshold uncertainty score0.708

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.001
Science and technology studies0.0010.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.009
GPT teacher head0.236
Teacher spread0.227 · 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