Goroutine lifecycle - Time & Space Complexity

Time Complexity: Goroutine lifecycle

O(n)

Understanding Time Complexity

When working with goroutines, it is important to understand how their execution time grows as we create more of them.

We want to know how the time cost changes when the number of goroutines increases.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

package main

import (
	"fmt"
	"sync"
)

func main() {
	var wg sync.WaitGroup
	n := 5
	wg.Add(n)
	for i := 0; i < n; i++ {
		go func(i int) {
			defer wg.Done()
			fmt.Println(i)
		}(i)
	}
	wg.Wait()
}
    

This code launches n goroutines, each printing a number, and waits for all to finish.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Starting and running n goroutines.
• How many times: Exactly n times, once per goroutine.

How Execution Grows With Input

As the number of goroutines n increases, the total work to start and complete them grows linearly.

Input Size (n)	Approx. Operations
10	About 10 goroutine starts and prints
100	About 100 goroutine starts and prints
1000	About 1000 goroutine starts and prints

Pattern observation: The total work grows directly with the number of goroutines.

Final Time Complexity

Time Complexity: O(n)

This means the time to start and complete all goroutines grows in a straight line as you add more goroutines.

Common Mistake

[X] Wrong: "Starting many goroutines happens instantly and does not add time."

[OK] Correct: Each goroutine takes some time to start and run, so more goroutines mean more total work and time.

Interview Connect

Understanding how goroutine count affects execution time helps you write efficient concurrent programs and explain your reasoning clearly.

Self-Check

"What if each goroutine launched another goroutine inside it? How would the time complexity change?"

Practice

1. What does a goroutine in Go allow your program to do?

easy

A. Make the program run slower

B. Automatically fix bugs in the code

C. Prevent the program from exiting

D. Run multiple functions at the same time

Solution

1. Step 1: Understand goroutine purpose

   A goroutine lets your program run functions concurrently, meaning at the same time.

2. Step 2: Compare options

   Only Run multiple functions at the same time correctly describes this behavior. Other options are incorrect or unrelated.

3. Final Answer:

   Run multiple functions at the same time -> Option D

4. Quick Check:

   Goroutine = concurrent execution [OK]

Hint: Goroutines run functions concurrently, like multitasking [OK]

Common Mistakes:

• Thinking goroutines slow down the program
• Believing goroutines prevent program exit automatically
• Assuming goroutines fix code errors

2. Which of the following is the correct syntax to start a goroutine for function doWork()?

easy

A. goroutine doWork()

B. go doWork()

C. start doWork()

D. run go doWork()

Solution

1. Step 1: Recall goroutine syntax

   In Go, prefixing a function call with go starts it as a goroutine.

2. Step 2: Check options

   Only go doWork() uses the correct syntax: go doWork(). Others are invalid.

3. Final Answer:

   go doWork() -> Option B

4. Quick Check:

   Start goroutine = go + function call [OK]

Hint: Use 'go' before function call to start goroutine [OK]

Common Mistakes:

• Using keywords like 'start' or 'run' instead of 'go'
• Writing 'goroutine' as a keyword
• Adding extra words before 'go'

3. What will be the output of this Go program?

package main
import (
  "fmt"
  "time"
)
func sayHello() {
  fmt.Println("Hello from goroutine")
}
func main() {
  go sayHello()
  fmt.Println("Main function finished")
  time.Sleep(100 * time.Millisecond)
}

medium

A. Main function finished

B. Hello from goroutine\nMain function finished

C. Main function finished\nHello from goroutine

D. No output

Solution

1. Step 1: Understand goroutine and main flow

   The goroutine runs sayHello() concurrently, printing "Hello from goroutine". The main function prints "Main function finished" immediately.

2. Step 2: Consider the sleep delay

   The time.Sleep pauses main to allow goroutine to run before program exits, so both prints appear.

3. Final Answer:

   Main function finished Hello from goroutine -> Option C

4. Quick Check:

   Sleep allows goroutine output after main print [OK]

Hint: Sleep main to let goroutine print before exit [OK]

Common Mistakes:

• Ignoring sleep causes goroutine output to miss
• Assuming goroutine prints before main
• Expecting no output without sleep

4. Identify the problem in this Go code snippet:

package main
import "fmt"
func main() {
  go func() {
    fmt.Println("Inside goroutine")
  }()
}

medium

A. The goroutine will never run because main exits immediately

B. Syntax error in anonymous function

C. Missing import for goroutine package

D. No problem, code runs fine

Solution

1. Step 1: Analyze goroutine lifecycle

   The main function starts a goroutine but then immediately exits, ending the program.

2. Step 2: Effect on goroutine execution

   Because main exits, the goroutine may not get time to run, so "Inside goroutine" might never print.

3. Final Answer:

   The goroutine will never run because main exits immediately -> Option A

4. Quick Check:

   Main exit stops goroutine early [OK]

Hint: Main must wait or goroutine may not run [OK]

Common Mistakes:

• Thinking goroutine runs after main exits
• Assuming syntax error in anonymous function
• Believing a special import is needed

5. You want to start 3 goroutines that each print their number (1, 2, 3). Which code correctly ensures each goroutine prints its own number without race conditions?

package main
import (
  "fmt"
  "time"
)
func main() {
  for i := 1; i <= 3; i++ {
    // Which option below is correct here?
  }
  time.Sleep(100 * time.Millisecond)
}

hard

A. go func(n int) { fmt.Println(n) }(i)

B. go func() { fmt.Println(i) }(i)

C. go func() { fmt.Println(i) }()

D. go func(n int) { fmt.Println(i) }(i)

Solution

1. Step 1: Understand variable capture in goroutines

   Loop variable i changes during iterations; capturing it directly in goroutine causes all to print last value.

2. Step 2: Use parameter to pass current value

   Passing i as a parameter n to the goroutine fixes this, so each prints its own number.

3. Final Answer:

   go func(n int) { fmt.Println(n) }(i) -> Option A

4. Quick Check:

   Pass loop variable as parameter to goroutine [OK]

Hint: Pass loop variable as function parameter to avoid capture issues [OK]

Common Mistakes:

• Capturing loop variable directly causing all prints same value
• Passing wrong variable to goroutine
• Confusing parameter and captured variable