3 ms·
My largest Golang deployment is a blender service. That's where I used the Goroutines and protocol buffers I mentioned earlier. Its speed is acceptable. My tak
by encoderer 14y ago
My largest Golang deployment is a blender service. That's where I used the Goroutines and protocol buffers I mentioned earlier.
Its speed is acceptable. My take on it is that this is a new language. Of course it doesn't have fully mature, fully optimized internals. And certainly part of the problem is that I haven't developed a full mastery of the language (Mastery is not a word i use lightly) so that will improve, too.
But if your experience is that you've built multi-threaded apps in Go that perform comparable to a c++ implementation then I'd love to know if you have any specific tips and also I suppose that means that we're not going to see any broad improvements in runtime performance?
- lobster_johnson 14y agoI recommend trying gccgo, the Go compiler for the GCC suite. (GCC 4.7.1 and later have Go built in.) In my experience it is (at -O2) much faster than Go's own compiler. GCC, after all, has because a bunch of advanced optimizers with a long history of development behind them, and Go's own compiler does not. My recolleciton is that Go's own compiler was intended as a "suboptimal but correct" reference compiler, but this may have changed.
- encoderer 14y agoAppreciate the tip -- sincerely.