MétaCan
Menu
Back to cohort
Record W2071072864 · doi:10.1145/2479942.2479944

A study of pricing for cloud resources

2013· article· en· W2071072864 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

VenueACM SIGMETRICS Performance Evaluation Review · 2013
Typearticle
Languageen
FieldComputer Science
TopicCloud Computing and Resource Management
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsBandwidth throttlingCloud computingRevenueComputer scienceSizingRevenue managementWork (physics)Position (finance)Resource (disambiguation)Dynamic pricingYield managementOrder (exchange)TRACE (psycholinguistics)Pricing strategiesOperations researchMicroeconomicsEconomicsFinanceEngineeringComputer network

Abstract

fetched live from OpenAlex

We present a study of pricing cloud resources in this position paper. Our objective is to explore and understand the interplay between economics and systems designs proposed by recent research. We develop a general model that captures the resource needs of various applications and usage pricing of cloud computing. We show that a uniform price does not suffer any revenue loss compared to first-order price discrimination. We then consider alternative strategies that a provider can use to improve revenue, including resource throttling and performance guarantees, enabled by recent technical developments. We prove that throttling achieves the maximum revenue at the expense of tenant surplus, while providing performance guarantees with an extra fee is a fairer solution for both parties. We further extend the model to incorporate the cost aspect of the problem, and the possibility of right-sizing capacity. We reveal another interesting insight that in some cases, instead of focusing on right-sizing, the provider should work on the demand and revenue side of the equation, and pricing is a more feasible and simpler solution. Our claims are evaluated through extensive trace-driven simulations with real-world workloads.

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.004
metaresearch head score (Gemma)0.002
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: Empirical · Consensus signal: Empirical
Teacher disagreement score0.986
Threshold uncertainty score0.502

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.002
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.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.075
GPT teacher head0.331
Teacher spread0.256 · 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