4 ms·
goroutines run in a single OS thread. Same reason for blocking threading on Java. Said this restriction maybe lifted in the future but I wouldn't hold my brea
by MatthewPhillips 16y ago
goroutines run in a single OS thread. Same reason for blocking threading on Java. Said this restriction maybe lifted in the future but I wouldn't hold my breath on that.
EDIT: Clarification, on goroutines run in a single OS thread on AppEngine.
- supersillyus 16y agoGoroutines still provide concurrency with a single thread. It's not that useful for CPU-bound stuff, but I'd imagine it should allow multiple concurrent GAE API calls (as they are just IO, and certainly async under the hood), or you could do CPU-bound stuff while waiting for IO.
- DennisP 16y agoFrom a google developer, responding to complaints about the new per-instance pricing: "If you are using Java, we just launched the ability to make your instances multi-threaded allowing you to use fewer instances to handle the same traffic" https://groups.google.com/group/google-appengine/browse_thread/thread/54261b447e165812?pli=1 https://groups.google.com/group/google-appengine/browse_thre... I'd be surprised if they didn't do the same with Go, by the time it reaches production status.