Prev Next

Golang / GoLang Concurrency Mastery Interview Questions

What is work stealing in Go's scheduler and why does it matter for performance?

Work stealing is the mechanism that keeps all Ps (logical CPUs) busy even when goroutine load is unevenly distributed. It is the key reason Go programs efficiently use all available CPU cores without manual thread pool management.

How it works: each P maintains a local run queue — a lock-free ring buffer of up to 256 runnable Gs. When a P's local queue is empty, instead of blocking, it steals approximately half the Gs from another P's local queue. It also checks the global run queue and the network poller.

// Scheduling check order when a P's local queue is empty:
// 1. Every ~61 ticks: check the GLOBAL run queue first
//    (prevents global queue goroutines from starving)
// 2. Local run queue (lock-free)
// 3. Work-steal from another random P (takes ~half its Gs)
// 4. Global run queue
// 5. Network poller (goroutines blocked on net I/O now ready)

// Demonstration: 4 CPUs, 1000 goroutines — load distributes automatically
var wg sync.WaitGroup
for i := 0; i < 1000; i++ {
    wg.Add(1)
    go func(id int) {
        defer wg.Done()
        // This goroutine may be stolen from one P to another
        time.Sleep(10 * time.Millisecond)
    }(i)
}
wg.Wait()

// Visualise stealing with execution tracer:
// f, _ := os.Create("trace.out")
// trace.Start(f); ...; trace.Stop()
// go tool trace trace.out  →  shows G→P migrations

Why the 61-tick global check? Without it, goroutines that land in the global queue (due to overflow or waking from syscalls) could starve while all Ps have busy local queues. The periodic check ensures fairness.

What does a P do when its local run queue is empty?
Why does Go check the global run queue every ~61 scheduling ticks rather than always checking local queues first?

More Related questions...

Explain Go's GMP scheduler model. What are M, P, and G and how do they interact? What is work stealing in Go's scheduler and why does it matter for performance? Why can Go run millions of goroutines while equivalent OS-thread workloads fail? What is the difference between unbuffered and buffered channels in Go? What happens when you send to, receive from, or close a nil or closed channel? How does the select statement work in Go and what are its key properties? What is a data race in Go, how do you detect it, and what are the three main fixes? When do you use sync.Mutex versus sync.RWMutex, and what are the critical usage rules? How does sync.WaitGroup work and what are the most common mistakes? What is sync.Once and what guarantees does it provide? What causes deadlocks in Go and how do you detect and prevent them? What are directional channels in Go and why use them in function signatures? What causes goroutine leaks and how do you prevent and detect them? Implement fan-out and fan-in concurrency patterns in Go. How do you use a nil channel in select to dynamically enable or disable cases? When should you use the sync/atomic package instead of sync.Mutex? Implement a bounded worker pool pattern in Go. What are the differences between time.After, time.NewTimer, and time.NewTicker, and which leaks resources? How does context.Context enable clean goroutine cancellation and why is 'defer cancel()' critical? How do you use a buffered channel as a semaphore to limit goroutine concurrency? What is the 'done channel' pattern and why has context.Context largely superseded it? What is the goroutine loop-variable capture bug and how do you fix it? How does golang.org/x/sync/errgroup simplify concurrent error handling? When should a channel carry 'chan struct{}' versus a typed value, and why is close() used for broadcast? What is GOMAXPROCS, how does it affect parallelism, and what is the container pitfall? How does Go's select handle multiple ready cases, and how do you implement true priority? What is sync.Cond and when do you use it instead of channels? Implement Go's canonical pipeline pattern with cancellation from the Go blog. What is Go's memory model and why does it matter for concurrent code? What is the check-then-act race condition (TOCTOU) and how do you fix it? What is asynchronous preemption in Go (1.14+) and why was it introduced? How do you safely use a map from multiple goroutines in Go? How do you use a buffered channel as a task queue with natural backpressure? How does Go handle goroutines that make blocking syscalls — what happens to M and P? Implement a simple publish-subscribe broker using Go channels. What is the lock-held-during-I/O anti-pattern and how do you fix it? Write a complete example of implementing operation timeouts in Go using select. How do you write tests that detect goroutine leaks automatically? Implement a concurrent word count across multiple files — a classic Go interview puzzle. How does GOMAXPROCS=1 change behaviour and when is it actually useful? How do you implement a high-performance sharded concurrent map in Go? What are the specific happens-before guarantees for channel operations in Go's memory model? How do you implement a hedged request pattern using select and goroutines? How does sync.Pool reduce GC pressure in high-throughput Go services? What is a livelock and how does it differ from a deadlock in Go programs? How do you implement backpressure in Go to prevent overloading downstream systems? Implement a lock-free stack using atomic CAS operations and explain the ABA problem. Summarise: channel vs mutex decision guide, and the top concurrency pitfalls.
Show more question and Answers...

GoLang Production Patterns and Web Standards Interview Questions

Comments & Discussions

Interviews Questions

About Javapedia.net

Javapedia.net is for Java and J2EE developers, technologist and college students who prepare of interview. Also this site includes many practical examples.

This site is developed using J2EE technologies by Steve Antony, a senior Developer/lead at one of the logistics based company.

Follow Javapedia updates

contact: javatutorials2016[at]gmail[dot]com

Kindly consider donating for maintaining this website. Thanks.

Copyright © 2026, javapedia.net, all rights reserved. · .

DMCA.com Protection Status