search

Golang Garbage Collector 101

Take a look at GC running visually

hashtag
Quick Look at Garbage Collector

A simple program that creates a byte array of 100000000 elements and lets print the memory allocations.

package main

import (
    "fmt"
    "runtime"
    "time"
)

func printStats(mem runtime.MemStats) {
    runtime.ReadMemStats(&mem)
    fmt.Println("mem.Alloc:", mem.Alloc)
    fmt.Println("mem.TotalAlloc:", mem.TotalAlloc)
    fmt.Println("mem.HeapAlloc:", mem.HeapAlloc)
    fmt.Println("mem.NumGC:", mem.NumGC)
    fmt.Println("-----")
}

func main() {
    var mem runtime.MemStats
    for i := 0; i < 2; i++ {
        s := make([]byte, 100000000)
        if s == nil {
            fmt.Println("Operation failed!")
        }
        printStats(mem)
    }
    time.Sleep(time.Second)
    // adding time.Sleep so that GC finishes it works and print out the output to terminal
}

hashtag
Understanding the code

There is a package in Golang standard library called runtimewhich contains alot of useful function like :

  • runtime.ReadMemStats(&mem)

  • runtime.GC()

Take a loot at : https://golang.org/pkg/runtime/arrow-up-right

hashtag
func ReadMemStatsarrow-up-right

ReadMemStats populates m with memory allocator statistics.

The returned memory allocator statistics are up to date as of the call to ReadMemStats. This is in contrast with a heap profile, which is a snapshot as of the most recently completed garbage collection cycle.

hashtag
func GCarrow-up-right arrow-up-right

GC runs a garbage collection and blocks the caller until the garbage collection is complete. It may also block the entire program.

Run this program using the following flag :

Output i receive [ don't get scared, will clean up ] :

Let look at the second run :

  • In first line : ignoring the value from CPU profiler, take a look at "95->95>0 MB". The first number is the heap size when the garbage collector is about to run. The second value is the heap size when the garbage collector ends its operation. The last value is the size of the live heap that is 0

  • It allocated 100081456 bytes of memory, more than the 100000000 becuase that is the length of slices we specified, and 100081456 bytes is the capacity of the slices or simply everytime you make a slices, some extra memory is allocated with it in case the size needs to expand in future.

  • Thus before running through the second iteration of the loop, it clears out the memory allocated during the first

PreviousMaps vs slicesNextThings Golang do differently

Last updated