Proposal: Intermediate: Talk: Go Runtime 3

[pshirali]

Type: Talk

Level: Intermediate

Duration (minutes, includes Q&A): 60 min

Abstract:

Go Runtime Part 3 - A look into Go's GC.

Links:

...

Intended Audience (optional)

Prerequisites

Recommended Learning

---

Speaker Bio

Name: Dinesh Kumar

---

Self Declaration:

Please replace the blank space within the square bracket with an x to tick the box.

• [x] I have read and understood the Go Community Code of Conduct
• [x] I have read and understood the StudyGroup Rules & Guidelines
• [x] I have already consulted and obtained clearance from all stakeholders about any Intellectual Property. I'm solely responsible for the content I present.

Proposed Dates: May 28th 2019

[pshirali]

28-03-2019 go study group -- Notes by @devdinu

=== gc agenda ===

• [x] mark and sweep

• [x] generational gc

  • [x] multiple generations https://blogs.msdn.microsoft.com/abhinaba/2009/03/02/back-to-basics-generational-garbage-collection/
  • [x] lower generations are collected frequently than higher gen
  • [x] writebarrier is needed here too (gen1 -> gen0 references)

• [x] compaction

• [x] stack rescanning (concurrent gc)

  • [x] dealing with changes after mark

• non generational, non compaction, concurrent gc (tricolor gc)

gosched, *global stack g - goroutines p - process (multiplexes g's) m - machine

1. mark - finding objects / mem which is in use
2. sweep (unreachable obje/mem could be freed)

=== questions: ===

• write barrier usecase
• tcmalloc (non-compaction)
• non-generational ?

=== links === https://making.pusher.com/golangs-real-time-gc-in-theory-and-practice/ (gc tricolor cycles with animation) https://github.com/golang/go/issues/17503 http://neodooth.me/post/2017-09-05-stack-re-scanning-in-go/ (great article on write barrier) https://groups.google.com/forum/#!topic/golang-nuts/kjiyv2mv2pu/discussion (golang nuts discussion) https://news.ycombinator.com/item?id=16699611