MétaCan
Menu
Back to cohort
Record W7126432418 · doi:10.21428/594757db.fe8b76cf

Automatic Reduction of Execution Trace Data Volume UsingGradient Boosting in Large-Scale Microservice Systems

2024· article· en· W7126432418 on OpenAlexaff
Amir Haghshenas, Naser Ezzati‐Jivan, Michel Dagenais

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware System Performance and Reliability
Canadian institutionsPolytechnique Montréal
Fundersnot available
KeywordsBoosting (machine learning)Volume (thermodynamics)TRACE (psycholinguistics)MicroservicesKey (lock)Robustness (evolution)Feature (linguistics)Reduction (mathematics)

Abstract

fetched live from OpenAlex

In the complex world of online services that rely on interconnected microservices, ensuring these components have the necessary resources for optimal performance is crucial. Traditionally, analyzing extensive logs and traces from these systems has been the method to model performance, but collecting too little or too much data can present challenges for accurate performance modeling. This highlights the need for a more efficient approach. Our study introduces a streamlined two-phase method that leverages gradient boosting algorithms to pinpoint key data features essential for predicting CPU and memory demands accurately. By focusing on feature importance, we were able to significantly reduce the amount of data required for analysis—by more than 69\%—without compromising, and in some cases enhancing, the accuracy of our models. This evaluation was significantly strengthened by employing a comprehensive dataset provided by Alibaba, illustrating the practical application and validation of our method in a real-world, large-scale microservice environment. Further analysis on our results reveal that most of the identified features for for data volume reduction were mostly focused on the critical aspects of a microservice architecture, notably inter-service communication and resource access patterns. Our findings demonstrate that by concentrating on the most influential features of the microservice architecture trace data, it is possible to maintain, and potentially improve, system performance modeling with substantially less data, presenting a promising research direction for resource optimization in large-scale microservice performance modeling.

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 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: Empirical
Teacher disagreement score0.956
Threshold uncertainty score0.360

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.0000.000
Scholarly communication0.0000.001
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.021
GPT teacher head0.270
Teacher spread0.249 · 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 teacher head, 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 routes1
Has abstractyes

Explore more

Same topicSoftware System Performance and ReliabilityFrench-language works237,207