Assessing QoS consistency in cloud-based software-as-a-service deployments
Bibliographic record
Abstract
Cloud-deployed Software-as-a-Service (SaaS) solutions have become a common global software deployment regime. For SaaS providers success is increasingly tied to social media feedback, customer reviews, and referrals. As such, ensuring sufficiently few users experience low (or poor) quality of service (QoS) levels has become an important concern. Cloud-based SaaS QoS is primarily driven by: i) the incoming workload's pace and complexity, ii) the SaaS system's design and implementation, and iii) the cloud platform's own induced QoS variabilities. Of these, SaaS software engineers generally have the least control over (iii), making it important to properly understand and quantify. This work empirically assesses (iii) by applying statistically rigorous QoS testing to an industry-held cloud-deployed SaaS system. Identical SaaS system instances are instantiated into the same commercial cloud platform and exercised via identical synthetic in-coming workloads. The resulting run-time QoS statistical distributions of each SaaS instance are then pairwise compared via distribution-free goodness-of-fit tests. A high degree of (iii) induced statistical dissimilarity is observed, suggesting significant care is required when seeking to make QoS envelope predictions from per-instance observed SaaS QoS results. This also suggests deeper more formal efforts may be required to better understand and characterize the cloud-induced SaaS QoS consistency issues that arise within modern SaaS deployments.
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.009 | 0.042 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.000 | 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".