Memory Management in Go: The good, the bad and the ugly - Liam Hampton

In this session, Liam delves into the crucial topic of memory management, providing a comprehensive overview of what it is, why it matters, and how to harness its power to write highly performant and cost-efficient code.

He navigates the intricacies of the Go memory model, highlighting its distinctions and similarities with other popular languages, whilst also explaining the use of built-in tools such as reserved keyword functions and pointers.

Liam will also share valuable best practices and illustrate key concepts with both good and bad coding examples. The overall objective of this talk is to provide you with an understanding of whats under the hood and empower you to take control of your code and write more efficient and performant code from the start.

[mateuszm]

Hmm I actually hoped for some GC internals in Go; this presentation gives a high level overview and only touches multiple topics.

[Strawberry_Htet]

I thought this talk will go deep dive into GC. This video only touches the high level concepts.

[zzFluke]

well it's really really high level stuff. Almost a quote from the talk: "Wonderful GC would come and clean all your memory for you, don't worry!"

[aleksandrkravtsov]

Sadly but "Golang manages memory with with memory management mechanisms, go and learn them somewhere else" is all you will get from this video

[williamgilmore]

Don’t waste your time watching this! I seldom am this harsh. There is minimal value in the information covered. At best, it is a time waste with a shill for CoPilot at the end. There are errors in it. The worst is that defer is scope by a code block where it is actually scoped at the function level. He absolutely states to not use global variables and subsequently states to reuse variables to minimize allocations without realizing that these two statements have conflicts in cases. Furthermore, he never references sync.Pool as an alternative means. There much better content available. much better

[robertfletcher]

08:00 isn't a leak/bug. thats the end of the program, the memory is about to be automatically de-allocated.

[sebastian]

Instead of watching this look for even freeman's 2018 presentation.