This is the part I was most interested in. It's my understanding that Goroutines are not currently implemented very efficiently and I wanted to see how the current implementation compares to a typical Python version.
Goroutines are "green threads", small threads managed by the Go runtime and scheduled within multiple OS processes. I've never seen any indication that they're inefficient; I regularly create and destroy thousands of goroutines in less than a second. Oh, and Go doesn't have a global interpreter lock, so I'd expect the threading to work better than in python.
Well, multiple goroutines can run in parallel, which isn't possible in CPython. That's a huge difference right off the bat, even if gc has some work left in optimizing the implementation.
(As far as non-concurrent code goes, gccgo is very well-optimized, because it's basically piggy-backing on the extensive optimizations of gcc over the decades.)
I haven’t measured."
This is the part I was most interested in. It's my understanding that Goroutines are not currently implemented very efficiently and I wanted to see how the current implementation compares to a typical Python version.