The document discusses Go memory management and how it differs from other languages like C, explaining that Go uses a garbage collected heap and stack per goroutine rather than malloc and free, and that values are passed by value while pointers and slices can be more complex due to being references to underlying data. Key aspects of Go memory include how structs are allocated, when data escapes to the heap, getting memory statistics, and performance differences between Go memory allocation and C malloc.

1. Go:memory
Ростислав Дзінько

2. About me
● Software Architect @ ZeoAlliance
● Interests: Python / C / C++ / Go / D
● Made Video Course

3. Memory
Differs

4. Heap & Frame & Stack
Heap = GC Function Frame
Goroutine
Stack
Go memory

5. Everything is
passed by value
Pointers & Values

6. Pointer & Value
Value
Pointer

7. Passing Slices are tricky
Values
int
float
bool
struct
...
Pointers
*int
*float
*bool
*struct
...
Values
Slices

8. Capacity: unappreciated Slices still tricky

9. Structs are aligned Фікус-Пікус

10. Where to allocate?
Heap vs Stack

11. -m
go tool 6g -m src/gomemory/main.go

12. Inlining = faster

13. Inlining: Switch vs If

14. Local Frame Stack

15. Escape to Heap

16. Move to Heap

17. WTF?
Goroutine Stack

18. Contiguous vs Fragment
Go 1.2 Go 1.3
Evolution

19. Stack Growth
Stack Growth
=
Reallocate
+
Copy
but
Lock-Free!
AVOID

20. Getting Statistics runtime.MemStats
Heap
Stack
General

21. Go:new vs C:malloc
A bit of C

22. C:malloc vs Go:new

23. Questions?
Thank You for
Attention