Paper: Heracles: Improving Resource Efficiency at Scale - High Scalability -

Underutilization and segregation are the classic strategies for ensuring resources are available when work absolutely must get done. Keep a database on its own server so when the load spikes another VM or high priority thread can't interfere with RAM, power, disk, or CPU access. And when you really need fast and reliable networking you can't rely on QOS, you keep a dedicated line. Google flips the

[moccos_info]

Google + Stanford“ better utilization of compute resources while complying service level objectives (SLOs) for latency-critical (LC) and best effort batch (BE) tasks”

[fcicq]

actually have read. see Memory Bandwidth Monitoring & Cache Allocation Technology in Vol 3B Part2 http://static.googleusercontent.com/media/research.google.com/en/us/pubs/archive/43792.pdf