GopherCon 2015: Go GC: Solving the Latency Problem - Rick Hudson

Channel:Gopher Academy · Length:22:51 · Published:2015-07-28 · Views:21730

Watch on YouTube

Summary

Rick Hudson's GopherCon 2015 talk on Go 1.5's new low-latency concurrent garbage collector. It covers the motivation, performance numbers, technical challenges and why the approach fits Go.

Why HN recommends it

Pointed to as the authoritative source on Go's GC pause improvements, and later revisited when GC latency claims were challenged.

you might also find Rick Hudson's talk on GC improvements in Go 1.5 interesting — HN, 2015

C, C++, Rust, Go & systems languages · Software performance & optimization · Compilers, interpreters & program analysis

Subtitles (excerpt)

okay so today we're going to talk about the go GC this is going to come out in a month in 1.5 in August um and we think we've got this latency problem solved for you and that's what we're going to talk about so before we go on I want to uh talk about my codefendants and my friends these are this is the Cambridge runtime team Austin this is uh a new hire he's a very big brained type of guy um sitting also next to him is Russ who we talked to we heard about this morning armor Hudson and David Chase uh just joined us a few months ago so that's the team and sometimes we have discussions about the other go the go you play with a board in little Pebbles and sometimes those discussions in this way the discussions about the language are much more amicable so um okay so let's talking about making go go okay so we have this concept of a virtuous cycle okay it's an economic term and basically it says that if we write software and the software would be written in go then our dream is that when the next piece of Hardware comes out from one of the hardware companies that software unchanged will run better meanwhile since we have this new great Hardware we're able to write better software and we're going to create this virtuous

On Hacker News

Go's TLS support should be greatly improved in Go 1.6 thanks to the performance work you referenced by Cloudflare. The licensing issue was resolved and the work was merged 11/10/2016[1] While GC will always carry a cost, great improvements have been made over the last year and continues to be an area of focus for each Go release. Rick Hudson gave a nice update on Go's GC improves at GopherCon 201… — kelseyhightower, 2016-01
If you liked this you might also find Rick Hudson's talk on GC improvements in Go 1.5 interesting: [VIDEO] [LINK] — shawnps, 2015-10
Oki, got it. Can't decide if that sounds like horrible conditions or a fun challenge =) For reference, the Go 1.5 GC propaganda: > Go 1.5, the first glimpse of this future, achieves GC latencies well below the 10 millisecond goal we set a year ago. Blog post: [LINK] Slide: [LINK] Talk: [VIDEO] Edit: Meanwhile, over in Java land they measure stop the world pauses in seconds , not milliseconds: [LI… — gizzlon, 2016-05
It looks like a few things in there could further reduce typical and peak pause times, by backgrounding more phases of the work and rescanning stacks late so it's less likely much marking has to happen in the pause. I'm less clear on this, but "embrace write barrier during scan" and the other pacing changes might also better spread out work during the concurrent phases. The pause improvements in … — twotwotwo, 2015-08
Wait, isn't Go devs said they solved GC latency problems [1]? (from 2015): "Go is building a garbage collector (GC) not only for 2015 but for 2025 and beyond: A GC that supports today’s software development and scales along with new software and hardware throughout the next decade. Such a future has no place for stop-the-world GC pauses, which have been an impediment to broader uses of safe and s… — deepsun, 2020-02

Related videos