Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

App Engine’s New Go 1.11 Runtime

blog.golang.org

Post reply on HN
Print view View original

71–80 of 101 posts

Re: App Engine’s New Go 1.11 Runtime

#71

Post by openbasic »

buss wrote: post #2

I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…

Vendoring! Modules! Finally. Do you have any examples with proposed solutions for local module setups, without having to rely on GOPATH changes?

Re: App Engine’s New Go 1.11 Runtime

#72

Post by eiieirurjdndjd »

wiradikusuma wrote: post #26
buss wrote: post #2

I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…

It's always been my impression that Go on GAE is the most lightweight compared to Java/Python, as it not "memory hungry" like Java nor "slow" like Python. Am I correct?

Nodejs might also be a good option. It’s comparable to go on a core for core basis, and IIRC GOMAXPROCS is 1 on GAE.

Re: App Engine’s New Go 1.11 Runtime

#73

Post by iamgopal »

buss wrote: post #2

I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…

Does context.background() works ?

Re: App Engine’s New Go 1.11 Runtime

#74

Post by eiieirurjdndjd »

pkroll wrote: post #70
tomcam wrote: post #48

Earlier quoted context omitted.

I would absolutely love those numbers too. Always wondered about the working set of a minimal program, and also one with database access.

Well, there's the Techempower benchmarks at: https://www.techempower.com/benchmarks/ You can go to the filter, turn off all languages but Go and Python, and get a general idea. There's also the old Computer Benchmark Game, which should be taken with a whole barrel of salt: https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

I actually looked at this before making my other comment. You’re absolutely right about the salt. One of the go benchmarks is basically pure cgo using vector intrinsics. It naturally blows idiomatic JS out of the water. So you might get those kind of results if that’s the kind of code you’re going to write, but it’s far from what I consider idiomatic. Another language’s proponent would be fair to point out that most languages have C FFIs.

Re: App Engine’s New Go 1.11 Runtime

#75

Post by iamgopal »

chrisbroadfoot wrote: post #65
deckarep wrote: post #40

Does this new classic+ environment now supersede the Flex environment? I’m curious because now it’s seems like there are 3 solutions. Although I really like the simplicity of this solution and the modernizing from the constraints of true classic mode.

(GCP Gopher here) If you can run within the standard environment, I'd suggest you do (but you should check pricing, etc to see if it suits). Especially if you want 0-1 scaling. I migrated golang.org from standard to flexible a couple weeks ago, primarily because of increased control over the runtime (custom Docker image) and increased instance sizes (configurable memory, CPU past the App Engine limits, which caps out…

Do you have blog post with data, number of instances etc previously and now ?

Re: App Engine’s New Go 1.11 Runtime

#76

Post by paulddraper »

chrisbroadfoot wrote: post #60
paulddraper wrote: post #57

Earlier quoted context omitted.

I thought Go was statically compiled....i.e. it doesn't have a separate runtime from the program. Does anyone have any elucidation?

Correct, Go's runtime is compiled into the program's binary. However, there's still an environment needed to run that binary. For Go on App Engine, this includes the sandbox (backed by gVisor) and the operating system (Ubuntu). We also tend to call everything in the toolchain the "runtime" - this includes the CLI for uploading and staging your app, and the builder used to compile your program. Not the strictest defin…

So App Engine is a build system as well?

Re: App Engine’s New Go 1.11 Runtime

#77

Post by asciimike »

B-Scan wrote: post #51
asciimike wrote: post #44

Earlier quoted context omitted.

(GAE PM) Cloud Endpoints currently runs on GAE Standard Gen 1 and GAE Flex. We're investigating a solution for GAE Standard Gen 2 (which go 1.11 is, along with python 3.7, node 8, etc.) and GCF.

Thanks for the clarification. Wasn’t aware that it works with Go on Standard Gen 1. Any ETA for Gen 2 or alpha signup?

Clarification: GAE Standard uses the Endpoints framework, which is Python and Java only (https://cloud.google.com/endpoints/docs/frameworks/about-clo...). Sorry for the confusion.

Flex uses ESP (https://github.com/cloudendpoints/esp), which is deployed as a sidecar, and works with any runtime.

As for EAP: unfortunately not. Personally, I'd like to see a managed version as opposed to the current framework or sidecar approach, as it'll be easier to implement across products, but that means it'll likely take a little longer.

Re: App Engine’s New Go 1.11 Runtime

#78

Post by TheDong »

openbasic wrote: post #71
buss wrote: post #2

I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…

Vendoring! Modules! Finally. Do you have any examples with proposed solutions for local module setups, without having to rely on GOPATH changes?

This is a go question, not an app engine question. See this page on the go wiki for an example of how to use go modules: https://github.com/kubernetes/kubernetes/pull/58098

Note: you need to have go1.11, and by default you need to be in a directory NOT in your $GOPATH for modules to work in go1.11

Re: App Engine’s New Go 1.11 Runtime

#79

Post by chrisbroadfoot »

eiieirurjdndjd wrote: post #72
wiradikusuma wrote: post #26

Earlier quoted context omitted.

It's always been my impression that Go on GAE is the most lightweight compared to Java/Python, as it not "memory hungry" like Java nor "slow" like Python. Am I correct?

Nodejs might also be a good option. It’s comparable to go on a core for core basis, and IIRC GOMAXPROCS is 1 on GAE.

(GAE Gopher)

GOMAXPROCS is not 1 for this new runtime. As far as I know, it's an entirely vanilla Go runtime.

Re: App Engine’s New Go 1.11 Runtime

#80

Post by chrisbroadfoot »

iamgopal wrote: post #73
buss wrote: post #2

I'm the tech lead and primary software engineer on the Go runtime. If you have any questions, please don't hesitate to ask! I'm super thrilled to announce that Go 1.11 is now available on App Engine! We now support... * vendoring * regular best-practice package structures * go modules * the regular Google Cloud client libraries: https://github.com/GoogleCloudPlatform/google-cloud-go This is a "second-generation" runt…

Does context.background() works ?

(GCP Gopher)

Yes, you don't need to use the appengine context for anything (except to access the services at google.golang.org/appengine/...)

You can use the standard net/http package to make HTTP requests, for example.

Post reply on HN