Bibliographic record
Abstract
The popularity of machine learning (ML) workloads have made GPU instance offerings ubiquitous in the cloud, introducing new challenges in managing, profiling, and optimizing GPU workloads. Cloud providers assign passthrough GPUs directly to virtual machines (VMs) for high performance, but doing so renders VM migration non-functional, limiting cloud operator ability to manage hardware resources. Existing general purpose GPU (GPGPU) and deep neural network (DNN) profiling tools are ineffective for heterogeneous CPU/GPU workloads like reinforcement learning (RL) since they only provide information about GPU kernel and DNN layer execution, and ignore CPU-side bottlenecks such as simulation. The lack of adequate profiling tools has led ML researchers to rely on naive costly cluster scale-up solutions to optimize RL training time, which can cost millions of dollars and are inaccessible to most ML researchers. In this dissertation, we build systems software for addressing these challenges. For management, we build Crane, a GPU virtualization middleware that achieves within 5% of passthrough GPU performance, requires no OS/application/hypervisor modifications, and can even enable migration between heterogeneous GPU targets. For profiling, we build RL-Scope, a cross-stack profiling tool tailored to RL workloads that breaks down low-level CPU/GPU training time scoped to high-level algorithmic operations (i.e., inference, simulation, backpropagation). We survey RL workloads across major workload dimensions (i.e., simulator, RL algorithm, DNN framework) and demonstrate that RL workloads suffer universally from low GPU utilization, and that na ̈ıve attempts to increase GPU utilization by parallelizing GPU inference requests are unsuccessful. For optimization, we propose two optimizations targeting the time-consuming data collection phase of RL training. First, GPU vectorization moves simulation from the CPU to the GPU to benefit from increased hardware parallelism, achieving a 1024× speedup over CPU implementations. Second, Simulator kernel fusion fuses multiple steps of simulation into a single GPU kernel launch to benefit from caching simulator state in fast GPU registers, obtaining a 11.3× speedup over an unfused GPU kernel. Both optimizations are orthogonal and can be combined for massive multiplicative speedups, and are more accessible to ML researchers since they do not rely on costly cluster scale-up
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.001 | 0.009 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.003 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
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".