On the Interplay between Network Traffic and Energy Consumption in Virtualized Environment: An Empirical Study
Bibliographic record
Abstract
Networking and virtualization are two key building blocks of modern cloud computing. The energy consumption of physical machines has been carefully examined in the past research, including the impact of network traffic. When it comes with virtual machines, the inter-play between energy consumption and network traffic however becomes much more complicated. The traffic are now generated by and exchanged between virtual machines (VMs), which could reside in different physical machines with their respective network interface cards (NICs), or share the same physical machine. When multiple VMs share a physical NIC, their traffic can interfere with each other, causing extra overhead. Yet the VM's allocation can be dynamic and they can even migrated across physical machines, thereby changing the traffic pattern. These factors combined make the network traffic highly diverse and dynamic, so is the corresponding energy consumption. A close examination on the network traffic and energy consumption in virtualized environments is thus of need. In this paper, we present an initial measurement study on the interplay between energy consumption and network traffic in representative virtualization environments. Our study reveals a series of unique energy consumption patterns of the network traffic in this context. We show that state-of-the-art virtualization designs noticeably increase the demand of CPU resources when handling networked transactions, generating excessive interrupt requests with ceaselessly context switching, which in turn increases energy consumption. Even when the physical machine is in an idle state, the VM network transactions will will incur remarkable energy consumption. Furthermore, even with identical number of VMs and amount of traffic on a physical machine, the energy consumptions vary significantly with different VM allocation strategies. Our close examination pinpoints the root cause, and offers new angles to revisit the existing resource usage and energy consumption models, so as to optimize the service provisioning as well as virtual machine placement and migration.
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.012 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".