Why concurrency matters in Ruby - See It in Action

Why concurrency matters in Ruby

📖 Scenario: Imagine you run a small online store. You want your website to handle many customers at the same time without slowing down. This is where concurrency helps your Ruby program do many things at once smoothly.

🎯 Goal: You will create a simple Ruby program that shows how concurrency lets your program do multiple tasks at the same time. This helps your store serve many customers quickly.

📋 What You'll Learn

Create a list of tasks representing customer orders

Set a limit for how many tasks can run at the same time

Use Ruby threads to process tasks concurrently

Print messages showing when each task starts and finishes

💡 Why This Matters

🌍 Real World

Concurrency helps websites and apps handle many users or tasks at once without slowing down.

💼 Career

Understanding concurrency is important for Ruby developers building fast, responsive applications.

1

Create a list of customer orders

Create an array called orders with these exact strings: 'Order 1', 'Order 2', 'Order 3', 'Order 4', 'Order 5'.

Ruby

# Create an array called orders with 5 order names
# Your code here

Hint

Use square brackets [] to create an array and put the order names inside quotes separated by commas.

2

Set the maximum number of concurrent tasks

Create a variable called max_threads and set it to 2 to limit how many orders can be processed at the same time.

Ruby

orders = ['Order 1', 'Order 2', 'Order 3', 'Order 4', 'Order 5']
# Set max_threads to 2
# Your code here

Hint

Just write max_threads = 2 on a new line.

3

Process orders concurrently using threads

Use a threads array to hold threads. Use a for loop with variable order to go through orders. Inside the loop, create a new thread that prints "Starting #{order}", sleeps for 1 second, then prints "Finished #{order}". Add the thread to threads. If the number of threads reaches max_threads, wait for the first thread to finish before continuing.

Ruby

orders = ['Order 1', 'Order 2', 'Order 3', 'Order 4', 'Order 5']
max_threads = 2
# Use threads to process orders concurrently
# Your code here

Hint

Use Thread.new to create a thread. Use threads.shift.join to wait for the oldest thread when max_threads is reached.

4

Print the final output showing concurrency

Run the program to print messages showing when each order starts and finishes. The output should show that up to 2 orders run at the same time.

Ruby

orders = ['Order 1', 'Order 2', 'Order 3', 'Order 4', 'Order 5']
max_threads = 2
threads = []
for order in orders
  threads = max_threads
    threads.shift.join
  end
end
threads.each(&:join)
# Run the program to see output

Hint

Run the program and watch the messages. You should see two orders starting before any finish, showing concurrency.

Practice

1. Why is concurrency important in Ruby programs?

easy

A. It allows the program to do multiple tasks at the same time, improving speed.

B. It makes the program use less memory.

C. It automatically fixes bugs in the code.

D. It changes the program's output format.

Solution

1. Step 1: Understand concurrency's purpose

   Concurrency lets a program handle multiple tasks simultaneously instead of one after another.

2. Step 2: Identify the benefit in Ruby

   This improves speed and responsiveness, especially when waiting for slow tasks or handling many users.

3. Final Answer:

   It allows the program to do multiple tasks at the same time, improving speed. -> Option A

4. Quick Check:

   Concurrency = multitasking speedup [OK]

Hint: Concurrency means doing many things at once [OK]

Common Mistakes:

• Thinking concurrency reduces memory usage
• Believing concurrency fixes bugs automatically
• Confusing concurrency with output formatting

2. Which of the following is the correct way to start a new thread in Ruby?

easy

A. Thread.new { puts 'Hello from thread' }

B. thread.start { puts 'Hello from thread' }

C. new Thread { puts 'Hello from thread' }

D. Thread.run { puts 'Hello from thread' }

Solution

1. Step 1: Recall Ruby thread syntax

   In Ruby, threads are created using Thread.new with a block of code.

2. Step 2: Check each option

   Only Thread.new { ... } is valid Ruby syntax to start a thread.

3. Final Answer:

   Thread.new { puts 'Hello from thread' } -> Option A

4. Quick Check:

   Thread.new starts threads [OK]

Hint: Use Thread.new with a block to start threads [OK]

Common Mistakes:

• Using incorrect method names like thread.start
• Trying Java-style thread creation syntax
• Confusing Thread.run with Thread.new

3. What will this Ruby code output?

thread = Thread.new { 5.times { |i| puts i; sleep 0.1 } }
thread.join
puts 'Done'

medium

A. Only 'Done' is printed

B. Done 0 1 2 3 4 (each number on its own line)

C. 0 1 2 3 4 Done (each number on its own line)

D. No output because of an error

Solution

1. Step 1: Understand thread execution

   The thread prints numbers 0 to 4 with a short pause between each.

2. Step 2: Effect of thread.join

   thread.join waits for the thread to finish before continuing to print 'Done'.

3. Final Answer:

   0 1 2 3 4 Done (each number on its own line) -> Option C

4. Quick Check:

   Thread prints numbers then main prints Done [OK]

Hint: thread.join waits for thread to finish before continuing [OK]

Common Mistakes:

• Thinking 'Done' prints before numbers
• Assuming no output due to thread
• Ignoring thread.join effect

4. What is wrong with this Ruby code that tries to use concurrency?

threads = []
i = 0
5.times do
  threads << Thread.new do
    puts i
  end
  i += 1
end
threads.each(&:join)

medium

A. The code will cause a syntax error.

B. The variable i is shared and may cause unexpected output.

C. threads.each(&:join) should be threads.join.

D. Thread.new is not the correct way to create threads.

Solution

1. Step 1: Analyze variable capture in threads

   The block uses variable i from the loop, which may change before thread runs, causing unexpected output.

2. Step 2: Identify concurrency issue

   Each thread may print the same or wrong i value because i is shared and changes quickly.

3. Final Answer:

   The variable i is shared and may cause unexpected output. -> Option B

4. Quick Check:

   Loop variable shared in threads causes bugs [OK]

Hint: Loop variables shared in threads cause unexpected values [OK]

Common Mistakes:

• Thinking Thread.new is wrong syntax
• Confusing threads.each(&:join) with threads.join
• Assuming syntax error without checking code

5. You want to speed up a Ruby program that downloads many files. Which concurrency approach is best and why?

hard

A. Use a single thread to download files one by one to avoid complexity.

B. Use threads but add sleep calls to slow down downloads.

C. Use multiple processes because Ruby threads cannot run in parallel at all.

D. Use threads to download files concurrently because IO waits can run in parallel.

Solution

1. Step 1: Understand IO-bound tasks and concurrency

   Downloading files is IO-bound and benefits from concurrency because waiting for network is slow.

2. Step 2: Choose concurrency method in Ruby

   Ruby threads can run IO tasks concurrently, improving speed without extra processes.

3. Final Answer:

   Use threads to download files concurrently because IO waits can run in parallel. -> Option D

4. Quick Check:

   Threads speed up IO waits in Ruby [OK]

Hint: Use threads for IO tasks to improve speed [OK]

Common Mistakes:

• Thinking Ruby threads never run in parallel
• Ignoring concurrency benefits for IO tasks
• Adding unnecessary sleep calls