Sadly, extended memory does not mean you can arbitrarily scale RAM versus cores for free. The memory above a certain ratio per vcpu is charged at a higher marginal rate. The focus of the product is for people that might only want more RAM, but if they add cpus something bad will happen (e.g., they don't have enough licenses for their software, or their code will literally crash). We'll try to update the docs to be clearer about this.
Disclosure: I work on Google Cloud.
I agree, the browser console is really fantastic. Does anyone know how this is implemented?
For what it's worth Linode has said (in Feb, 2017) that they will be announcing block storage in the coming months.
https://blog.linode.com/2017/02/14/high-memory-instances-and...
After all it's one of the main reasons why I prefer Digital Ocean for small projects.
I recently transitioned off of Linode (after about a decade?!) to Google. Largely, this was because I needed a lot more disk space to mirror some large public databases, and it was significantly cheaper to do this with Google than it would have been with Linode. This is because Linode couples the disk space with both the RAM and the number of processors. I needed more disk, and would have liked more RAM, but had no use for more processors.
With this announcement, Google has now decoupled the RAM from the number of processors, which is a development I'll be taking advantage of.