MétaCan
Menu
Back to cohort
Record W2783223655 · doi:10.1109/bigdata.2017.8258159

Towards MapReduce based Bayesian deep learning network for monitoring big data applications

2017· article· en· W2783223655 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 institutionsCarleton University
Fundersnot available
KeywordsComputer scienceBig dataScalabilityCloud computingSoftwareAnalyticsDeep learningBayesian networkMachine learningData miningArtificial intelligenceDistributed computingDatabaseOperating system

Abstract

fetched live from OpenAlex

One of the most commonly used ways to monitor execution of software applications is by analyzing logs. Logs are execution foot-print of software applications that are produced and stored for real-time or post-execution analysis of execution. With the software applications becoming large, complex, distributed, web-scale, also called as big data applications, logs produced by such software applications are also large-scale. That means, such logs are large in volume, velocity and variety. That makes it crucial to have such logs analyzed in an automated, scalable and effective manner to ensure high veracity and have analytics with high value. In this paper, we present our proposed solution of a formal model for organizing and structuring logs. We then present a Bayesian deep learning network based analysis approach that utilizes the formal model for logs to detect and predict any possible faults and consequences of such faults. Moreover, we also present our MapReduce based distributed, parallel, single-pass and incremental approach to build, train and execute the proposed Bayesian deep learning framework. This helps in effective processing of logs on cloud platforms and therefore efficient handling of logs that are produced at the scale of big data by big data applications.

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: Other design · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.919
Threshold uncertainty score0.990

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.0010.000
Scholarly communication0.0000.001
Open science0.0030.001
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.063
GPT teacher head0.314
Teacher spread0.252 · 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