SDN-Based virtual networking Consistently Fast - Fast VM Provisioning - Consistent Performance Cost Effective - Sub-Hour Billing - No IOPS charges for Block Storage - VMs not required for Load balancing Google Compute Engine
8 More CPU (Shared) 16 Instances to suit diverse workloads 32 Compute Engine VMs: • Debian, CentOS, SUSE, RHEL, Ubuntu, Windows (Beta • shared core or 1 - 32 cores • Up to 208 GB of RAM
Balancing Single IP per forwarding rule No prewarming needed; goes from 0 to full- throttle in seconds Detects unhealthy virtual machines instances Balance loads across regions Routes traffic to the closest virtual machine Supports content-based routing
• public: static and ephemeral • internal: ephemeral with automatic DNS • Network groups & firewall rules • rules applied to instances via tags • Gateways, routing and VPNs Networking Internet Networking
Managed Instance Group VM VM VM Managed Instance Group • Grouping of identical VM instances • Provisioned and monitored by Instance Group Manager • Instance Templates separate configuration from provisioning Instance Templates
Update VM VM VM New Template Managed Instance Group • Grouping of identical VM instances • Provisioned and monitored by Instance Group Manager • Instance Templates separate configuration from provisioning • Rolling Updates applied by instance Group Updater Instance Group Updater
etc. More Cost Effective • Flat pricing: < 50% regular VM rates Reasonable, Predictable Limitations • 24h uptime limit • Chance of early preemption by system (~10-20%) ◦ No preemptions due to other customers’ Preemptible VM requests • Pre-termination notice to allow for clean shutdown Preemptible VMs: What Batch
improve fleet allocation efficiency • Google can pass on the savings to you: win-win! “Regular” VMs are Suboptimal for Batch Use Cases • Always-on, infinite duration nature is not needed for batch type jobs • 99.95% continuous uptimes are designed for “serving” needs, not batch • Embarrassingly parallel jobs are often fault-tolerant to loss of worker nodes • Batch jobs might not hit best sustained use pricing thresholds Preemptible VMs: Why Batch