GIL (Global Interpreter Lock) impact in Ruby - Mini Project: Build & Apply

Understanding GIL (Global Interpreter Lock) Impact in Ruby

📖 Scenario: You are working on a Ruby program that needs to perform multiple tasks at the same time. You want to see how Ruby's Global Interpreter Lock (GIL) affects running threads concurrently.

🎯 Goal: Build a simple Ruby program that creates multiple threads to count numbers. You will observe how GIL impacts the execution of these threads.

📋 What You'll Learn

Create a variable to hold a shared counter

Create a variable to hold the number of threads

Create multiple threads that increment the shared counter

Print the final value of the shared counter

💡 Why This Matters

🌍 Real World

Understanding GIL helps developers write better concurrent Ruby programs, especially when working with threads for tasks like web servers or background jobs.

💼 Career

Many Ruby developer roles require knowledge of threading and concurrency to optimize application performance and avoid bugs related to shared data.

1

Create a shared counter variable

Create a variable called counter and set it to 0.

Ruby

# Your code here

Hint

Use a simple variable assignment to start the counter at zero.

2

Set the number of threads

Create a variable called thread_count and set it to 5.

Ruby

counter = 0
# Your code here

Hint

Use a variable to store how many threads you want to create.

3

Create threads to increment the counter

Create an array called threads and use a thread_count.times do |i| ... end loop to create threads. Each thread should increment counter 1000 times using counter += 1.

Ruby

counter = 0
thread_count = 5
# Your code here

Hint

Create threads inside a loop and make each thread add 1 to the counter 1000 times. Use threads.each(&:join) to wait for all threads to finish.

4

Print the final counter value

Write puts counter to display the final value of counter after all threads finish.

Ruby

counter = 0
thread_count = 5
threads = []
thread_count.times do |i|
  threads << Thread.new do
    1000.times do
      counter += 1
    end
  end
end
threads.each(&:join)
# Your code here

Hint

Use puts counter to print the final count after all threads complete.

Practice

1.

What does the Global Interpreter Lock (GIL) in Ruby do?

easy

A. Automatically speeds up all multi-threaded Ruby programs

B. Allows multiple threads to run Ruby code simultaneously

C. Prevents any threads from running in Ruby

D. Allows only one thread to execute Ruby code at a time

Solution

1. Step 1: Understand the role of GIL

   The GIL is a lock that ensures only one thread runs Ruby code at once.

2. Final Answer:

   Allows only one thread to execute Ruby code at a time -> Option D

3. Quick Check:

   GIL = single-thread execution [OK]

Hint: GIL means one thread runs Ruby code at a time [OK]

Common Mistakes:

• Thinking GIL allows true parallel Ruby code execution
• Believing GIL stops all threading
• Assuming GIL speeds up multi-threading

2.

Which Ruby code snippet correctly starts two threads that print numbers?

Option A:
threads = [Thread.new { puts 1 }, Thread.new { puts 2 }]
threads.each(&:join)

Option B:
Thread.new { puts 1 }
Thread.new { puts 2 }

Option C:
threads = Thread.new { puts 1 }
threads = Thread.new { puts 2 }
threads.join

Option D:
Thread.start { puts 1 }
Thread.start { puts 2 }

easy

A. Creates two threads and waits for both to finish

B. Creates two threads but does not wait for them

C. Creates one thread twice, only waits for last

D. Uses undefined Thread.start method

Solution

1. Step 1: Analyze thread creation and joining

   Creates two threads and waits for both to finish. Creates two threads and calls join on both, ensuring both finish.

2. Final Answer:

   Creates two threads and waits for both to finish -> Option A

3. Quick Check:

   Thread.new + join = wait for threads [OK]

Hint: Use join to wait for all threads to finish [OK]

Common Mistakes:

• Not calling join and missing thread completion
• Overwriting thread variables losing references
• Using non-existent Thread.start method

3.

What will be the output of this Ruby code considering the GIL?

count = 0
threads = 5.times.map do
  Thread.new do
    1000.times { count += 1 }
  end
end
threads.each(&:join)
puts count

medium

A. 5000

B. 1000

C. May be less than 5000 due to race conditions

D. 0

Solution

1. Step 1: Understand thread increments with GIL

   GIL allows one thread at a time, but count += 1 is not atomic and can cause race conditions.

2. Final Answer:

   May be less than 5000 due to race conditions -> Option C

3. Quick Check:

   Non-atomic increments + threads = race condition [OK]

Hint: GIL doesn't prevent race conditions on shared data [OK]

Common Mistakes:

• Assuming GIL makes increments atomic
• Expecting exact 5000 without synchronization
• Ignoring thread interference on variables

4.

Identify the problem in this Ruby code using threads and fix it:

count = 0
threads = 3.times.map do
  Thread.new do
    100.times { count += 1 }
  end
end
threads.each(&:join)
puts count

medium

A. Add a Mutex to synchronize increments

B. Remove threads and run increments sequentially

C. Use Thread.kill to stop threads early

D. No problem, code is correct

Solution

1. Step 1: Identify race condition on count variable

   Multiple threads increment count without synchronization causing race conditions.

2. Final Answer:

   Add a Mutex to synchronize increments -> Option A

3. Quick Check:

   Mutex prevents race conditions [OK]

Hint: Use Mutex to protect shared data in threads [OK]

Common Mistakes:

• Ignoring race conditions on shared variables
• Trying to kill threads instead of synchronizing
• Assuming GIL handles all thread safety

5.

You want to speed up a CPU-heavy Ruby program using threads. Considering the GIL, what is the best approach?

hard

A. Disable the GIL in Ruby settings

B. Use multiple processes instead of threads

C. Use threads only for I/O tasks, not CPU tasks

D. Use more threads since GIL allows parallel CPU work

Solution

1. Step 1: Understand GIL impact on CPU-bound threads

   GIL allows only one thread to run Ruby code at a time, so threads don't speed up CPU-heavy tasks.

2. Final Answer:

   Use multiple processes instead of threads -> Option B

3. Quick Check:

   Processes bypass GIL for CPU parallelism [OK]

Hint: Use processes, not threads, for CPU speedup in Ruby [OK]

Common Mistakes:

• Believing threads run CPU tasks in parallel with GIL
• Trying to disable GIL (not possible in standard Ruby)
• Using threads for CPU tasks instead of I/O