Some interesting responses to that "Go GC sucks" article that's been making the rounds https://groups.google.com/forum/#!topic/mechanical-sympathy/JJTUs_jXw5A …https://groups.google.com/forum/#!topic/golang-nuts/DyxPz-cQDe4 …
-
-
lots of Go CPU hours at Google are batch jobs, so the team wants throughput. The recent insight is low-pause is not nice but vital.
-
when deploying a server at Google focus is on controlling long-tail metrics. GC pauses break the tail, and so are a bug.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.