Exploring Emerging Industry Trends for Large-Scale Software System Performance Predictability: The Role of Apache and Xen
Bibliographic record
Abstract
Modern societies critically depend on numerous large-scale cloud-deployed distributed software systems (LDSSs), whether in social media and on-line games, banking and finance, business-to-business systems, data science and AI, etc. This core reliance is accelerating the software engineering need to capital-“E” Engineer system such that they behavior predictably in the real-world at their full operational scales. This work applies Monte Carlo simulation to assess and quantify the impacts of recent industry technology trends on LDSS performance predictability. Specifically, we show that technologies such as Apache Storm, Apache Spark and Xen's recent real-time operating system (RTOS) hypervisor introduction, work to produce more predictable LDSS run-time behaviors. The implications of these observations on LDSS management approaches, such as Kubernetes and Docker Swarm, are then discussed. All simulations are conducted via OMNet++ and its INET network framework for an industry held LDSS against a selected range of commonplace scenarios. To our knowledge this is the first work to seek to quantify emerging industry solutions against the specific concern of their impacts on LDSS run-time performance predictability.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.008 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".