News for hackers. Stuff that matters.
Re:Go GC: Solving the Latency Problem in Go 1.5 by eggnet on Wednesday July 08, 2015 @06:12PM (#9854954)
Yes, I have. We used go in a system that had to keep track of essentially large hashes containing popularity / scoring information, in addition to what were effectively routing tables, and ran into >500ms pauses.

At scale, it seemed the largest part of the complexity of go was manipulating data structures and code to avoid gc pauses. With sufficient work we may have been able to decrease the pauses sufficiently, but we also ran into raw request per second numbers that were lower than we liked.

The direction we have taken was to switch to C++ for this application. Having said that, the gc pauses were the primary reason for the change.

Re:Go GC: Solving the Latency Problem in Go 1.5 by jerf on Wednesday July 08, 2015 @08:37PM (#9855548)
If it's possible, and you're interested in trying, it would be interesting to pull that code out and try it again with Go 1.5, if it's easy.

If you've got a C++ solution, I would not suggest under any circumstances short of Go suddenly and frankly mysteriously blowing the doors off of C++ that you switch... I'm just saying it would be an interesting comparison.

Re:Go GC: Solving the Latency Problem in Go 1.5 by eggnet on Thursday July 09, 2015 @01:11AM (#9856257)
I'll be recommending we try it in a lab with go 1.5, absolutely.
Re:Go GC: Solving the Latency Problem in Go 1.5 by bjourne on Wednesday July 08, 2015 @09:18PM (#9855686)
Why didn't you just use Java? Hotspot has been optimized for over a decade to make (among other things) gc pauses as manageable as possible. And there are other runtimes (http://www.azulsystems.com/) specifically optimized for low latency. The poor quality of Go's GC were never a secret.
Re:Go GC: Solving the Latency Problem in Go 1.5 by nulltype on Wednesday July 08, 2015 @06:25PM (#9855009)
Ah, too bad. Do you know what sort of heap sizes you got those pauses at?
Re:Go GC: Solving the Latency Problem in Go 1.5 by eggnet on Thursday July 09, 2015 @01:12AM (#9856260)
About half a gig resident memory.
Re:Go GC: Solving the Latency Problem in Go 1.5 by Skinney on Thursday July 09, 2015 @05:09AM (#9856867)
So Go's GC spent 1ms per MB?
Re:Go GC: Solving the Latency Problem in Go 1.5 by nulltype on Thursday July 09, 2015 @04:34PM (#9860490)
According to this graph: https://pbs.twimg.com/media/CJatKFQUkAE5qcR.png:large

It's about 0.3ms per MB, so 1ms isn't that different.

Re:Go GC: Solving the Latency Problem in Go 1.5 by danieldk on Thursday July 09, 2015 @03:05AM (#9856539)
x86 or x86_64?
Re:Go GC: Solving the Latency Problem in Go 1.5 by eggnet on Thursday July 09, 2015 @09:56AM (#9857840)
x86_64