MétaCan
Menu
Back to cohort
Record W4409724185 · doi:10.1109/ucc63386.2024.00058

Algorithmic Fault Impact Evaluation in Mobile Computation Offloading

2024· article· en· W4409724185 on OpenAlexafffund
Marzieh Ranjbar Pirbasti, Olivia Das

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicIoT and Edge/Fog Computing
Canadian institutionsToronto Metropolitan University
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsComputer scienceComputation offloadingComputationMobile computingEmbedded systemComputer networkEdge computingAlgorithmInternet of Things

Abstract

fetched live from OpenAlex

Offloading computation-intensive applications from a mobile device to remote servers can improve the response time of the mobile device as well as its battery life. However, the benefits of computation offloading can be affected by faults in computation resources and network links, making resource management and task allocation even more challenging when fault tolerance is a consideration. While several mechanisms exist for protecting against such faults, fault-tolerance mechanisms typically introduce overheads, creating a challenge for efficient resource management in computation offloading. To reduce the overheads of fault-tolerance mechanisms in computation offloading, these mechanisms can be selectively applied to parts of the application with the highest fault impact. This necessitates the identification of such parts, which is a complex and time-consuming undertaking. In this paper, we propose a novel algorithmic approach tailored for cloud resource management that can evaluate the fault impact of tasks of an application, eliminating the need for time-consuming fault injection simulations. This approach enables more rapid analysis of an existing scenario, as well as more efficient exploration of alternative resource allocations. The proposed approach is evaluated on both an example workflow graph and a real face recognition application, and the results are verified against fault injection simulations. We also present a case study and show how the insights obtained from this analysis can be used to selectively apply fault-tolerance mechanisms to tasks with the highest fault impact within an application, to better manage and utilize additional cloud resources when designing for improved fault tolerance.

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.001
metaresearch head score (Gemma)0.005
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.006
Threshold uncertainty score0.012

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0010.005
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.000
Science and technology studies0.0010.001
Scholarly communication0.0010.001
Open science0.0010.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0020.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.026
GPT teacher head0.350
Teacher spread0.325 · 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 designSimulation or modeling
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

Citations0
Published2024
Admission routes2
Has abstractyes

Explore more

Same topicIoT and Edge/Fog ComputingFrench-language works237,207