Skylake now GA on GCE
cloudplatform.googleblog.com
cloudplatform.googleblog.com
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.
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.
- Skylake is now generally available
- Broadwell is now globally visible
- "Extended Memory" custom machine types are now in Beta
I decided to focus on Skylake as GA for the title, but depending on your interest these other announcements may be good to know as well. In particular, this changes the historical "us-central1-a is the oldest zone" into "us-central1-a is a better choice than 1-f".
Disclaimer: I work on Google Cloud (and want to sell you cores)
[Edited: I always forget newlines]
Can you share exactly what you do on GCE?
I used to work on Compute Engine itself. I led the team that built and launched Preemptible VMs, and I still participate in its upkeep / improvements. So I generally still write little bits of code that nobody else wants to (especially monitoring and other cleanup type work).
About a year ago we started an Office of the CTO with me as the first "hire". So I transitioned from building new things and writing code much of the time (Note: Many at Google will snicker at this, as I am routinely teased for being a pseudo-PM) to talking to high-profile customers most of the time (think CTO / VP Eng types). We usually talk through where they are, what challenges they have, and whether or not GCP can actually fulfill their needs today (and as my group focuses on candor, we certainly say "You shouldn't migrate to us until we do X, Y, and Z, or you rewrite Foo").
I just hang out on HN as I like the dialogue :).
My team is composed of a mix of Google engineers that can (kind of) talk to people, and recovering CXO types from various industries (Finance, Healthcare, etc.). Each of us try to only work deeply with 1-3 customers at once, while SAs are usually focused on more broadly applicable solutions.
We all weave in and out depending on personal relationships with customers and individual skill sets, but we're all behind trying to make our customers successful regardless of role or title.
Might you have a link for this role? Do you have a way to get in touch? I didn't see any details in your profile.
https://careers.google.com/jobs#!t=jo&jid=/google/solutions-...
[EDIT] According to another Googler in this thread, the address is actually etally@google.com.
The email you're looking for is etally@
You folks should really have a utility on the default images (maybe call it `seppuku` or `dienow`) which sends an "o" to /proc/sysrq-trigger; using that has allowed me to time shutdowns to within a couple seconds at worst (though there is an unfortunate discrepancy between the account logs, which show the accurate node shutdown time, and the instance logs, which only show it a few seconds later).
N.B.: My use case is batch jobs that have a significant amount of output bytes, so I don't care about the "quality" of the bandwidth.
And for those who aren't aware, Google is charging about two orders of magnitude more than market rates for Internet egress.
In Europe their pricing is even less competitive.
It's insane how much they charge for bandwidth and it severely limits the usefulness of the service.
I guess that might be the point though. If egress is expensive, you're encouraged to keep everything inside GCP.
EDIT - mods - any chance of a title edit? Search engines would appreciate that as much as humans.
You can safely bet anyone here will know what CPU stands for. But this title is just badly written and lazy. I actually managed to figure it out after a couple of seconds of staring but the point is - I shouldn't have to.
My biggest pet peeve is that you can't start 64-core instances with a trial account, even if you have lots of credit.
We still have some things on Skylake we're going to do beyond today's announcement, so today is really "Welcome!".
Disclaimer: I work on Google Cloud.
$ gcloud container node-pools create skylake --cluster montana --image-type gci --machine-type n1-standard-4 --zone us-central1-b --min-cpu-platform "Intel Skylake"
ERROR: (gcloud.container.node-pools.create) unrecognized
arguments:
--min-cpu-platform
Intel SkylakeDisclosure: I work on Google Cloud.
Can you give more details about this?
I'm not saying it's hard to understand what to do when new ones come out, but for each architecture there's a new machine family. GCE has only historically provided n1-whatever and you got whatever CPU platform we had in that specific building.
Still waiting for the AWS c5 instance: https://aws.amazon.com/about-aws/whats-new/2016/11/coming-so...
I know this may be a rare use-case, but is it possible to allow creating VM instances with more than 13GB of memory and only two cores?
I'd like to do 2 cores and 24GB for example.
Also, my project's are not seeing the new UI changes (cpu platform and extend memory), is this still rolling out?
As for extended memory, as I clarified elsewhere, while you can make a 2x24 it won't be saving you money compared to having the cores. I forget if this is made clear in the docs, but via the API this is laundered through machine types as custom-2-24000-ext.
What now what on what?
That's a great idea for a title of this item :)