|
|
|
|
|
by floatrock
2248 days ago
|
|
Great collab with Google! They've been probably the most serious corporate wrt getting all-renewable offsets for their operations... this is helping them reach the next milestone where the renewable offsets are time-matched. Great example of being serious about this stuff rather than just greenwashing. It sounds like this project is for their own operations. Have you guys thought about how to offer this closer to a turnkey cloudops SASS / API? What kinds of abstractions would you present to developers building non-time-critical compute loads? Could be a great differentiator for GCP vs. AWS (I have heard of some companies choosing GCP over AWS due to Google's green energy cloud). And for you guys, the only thing better than Google being a customer is all of Google's customers being your customers. |
|
If a data center has (roughly, to a first-order approximation) fixed compute capacity at any point in time, and we assume that any capacity not being used by Google themselves is made available to GCP, then wouldn't Google reserving the "green" hours for themselves drive the remaining "dirty" hours onto the GCP spot markets?
Is there a cloud market design that addresses this tension between maximizing utilization and having desirable or 'premium' compute hours?