I installed Google Go as root on Raspbian by typingrichrarobi wrote: Hardest part so far was setting up the go workplace directory structure (my understanding vs their very slightly confusing instructions)
Sorry about that, pretty typical for me. I don't know when to shut up .That's a pretty long post considering "I think any discussions concerning Go are pretty ridiculous IMO."
And that case you really should check out 1.5+. They've made some of the biggest GC improvements yet there, especially with regards to "stuttering" behaviour. Here's Rick Hudson giving a talk about the GC improvements at Gophercon 2015. I thought it was a nice overview of what they're trying to achieve, and it doesn't try to hide the compromises they made, etc.The show stopper for me at the time was the garbage collection stutters and poor performance in the particular task I wanted to use it for.
The improvements to the garbage collector described by Rick Hudson in the talk that was linked to above appear very significant.TheGameSquid wrote:They've made some of the biggest GC improvements yet there, especially with regards to "stuttering" behaviour. Here's Rick Hudson giving a talk about the GC improvements at Gophercon 2015.
For my FFT it appears much of the slowdown was due to mandatory bounds checking on array slices. A syntactically complicated way to avoid the bounds checking using "unsafe pointers" was discussed on the golang forumnatdm wrote:I thought Go was supposed to be faster than C?
I think the difference is that malloc/free are called when the programmer wants them to be called, and commonly for a single item only.
Users browsing this forum: Google [Bot] and 6 guests