Why Ractor for true parallelism in Ruby? - Purpose & Use Cases

The Big Idea

What if your Ruby program could run many tasks at the same time without crashing or slowing down?

The Scenario

Imagine you have a big puzzle to solve, but you only have one pair of hands to put the pieces together. You try to do everything step by step, but it takes a long time and sometimes you get tired or distracted.

The Problem

When you try to run many tasks at once using just one thread, they actually take turns instead of working at the same time. This makes your program slow and sometimes buggy because tasks can interfere with each other.

The Solution

Ractor lets you create separate workers that truly run at the same time without stepping on each other's toes. Each worker has its own space, so they don't share data directly, avoiding mistakes and speeding up your program.

Before vs After

✗ Before

threads = []
10.times do |i|
  threads << Thread.new { puts "Task #{i} running" }
end
threads.each(&:join)

✓ After

ractors = []
10.times do |i|
  ractors << Ractor.new(i) { |num| "Task #{num} running" }
end
ractors.each { |r| puts r.take }

What It Enables

With Ractor, your Ruby programs can truly do many things at once, making them faster and more reliable for heavy work.

Real Life Example

Think of a busy kitchen where each chef works independently on different dishes without bumping into each other, so meals get ready faster and without mistakes.

Key Takeaways

Manual multitasking in Ruby uses threads that share memory and can cause slowdowns or bugs.

Ractor creates isolated workers that run in parallel safely and efficiently.

This helps programs handle heavy tasks faster by truly doing many things at once.

Practice

1. What is the main purpose of using Ractor in Ruby?

easy

A. To run code truly in parallel on multiple CPU cores

B. To create graphical user interfaces

C. To handle database connections

D. To write single-threaded scripts

Solution

1. Step 1: Understand Ractor's role

   Ractor is designed to enable true parallel execution in Ruby, using multiple CPU cores.

2. Step 2: Compare options

   Options A, B, and C do not relate to parallelism or CPU core usage.

3. Final Answer:

   To run code truly in parallel on multiple CPU cores -> Option A

4. Quick Check:

   Ractor = true parallelism [OK]

Hint: Ractor means real parallel tasks in Ruby [OK]

Common Mistakes:

• Confusing Ractor with threads
• Thinking Ractor is for UI or database
• Assuming Ractor runs code sequentially

2. Which of the following is the correct way to create a new Ractor in Ruby?

easy

A. Ractor.new { puts 'Hello from Ractor' }

B. Thread.new { puts 'Hello from Ractor' }

C. Process.spawn { puts 'Hello from Ractor' }

D. Fiber.new { puts 'Hello from Ractor' }

Solution

1. Step 1: Identify Ractor creation syntax

   Ractor is created using Ractor.new with a block of code to run in parallel.

2. Step 2: Eliminate other options

   Thread, Process, and Fiber are different concurrency tools, not Ractor.

3. Final Answer:

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

4. Quick Check:

   Use Ractor.new to create Ractors [OK]

Hint: Ractor.new starts a parallel task [OK]

Common Mistakes:

• Using Thread.new instead of Ractor.new
• Confusing Process.spawn with Ractor
• Using Fiber.new which is cooperative, not parallel

3. What will be the output of this Ruby code using Ractor?

r = Ractor.new { 5 * 5 }
result = r.take
puts result

medium

A. RactorError

B. 5 * 5

C. nil

D. 25

Solution

1. Step 1: Understand Ractor block execution

   The block { 5 * 5 } runs inside the Ractor and returns 25.

2. Step 2: Use take to get the result

   r.take receives the value returned by the Ractor block, which is 25.

3. Final Answer:

   25 -> Option D

4. Quick Check:

   Ractor returns 25, take receives it [OK]

Hint: Ractor block returns value, take fetches it [OK]

Common Mistakes:

• Expecting string '5 * 5' instead of calculation
• Confusing take with yield
• Assuming nil or error without communication

4. Identify the error in this Ractor code snippet:

r = Ractor.new do
  Ractor.yield 10
  20
end
puts r.take
puts r.take

medium

A. Ractor.new requires arguments

B. Second r.take call will cause Ractor::Closed error

C. No error, code runs fine

D. Calling Ractor.yield inside Ractor block is invalid

Solution

1. Step 1: Understand Ractor.yield and r.take

   Ractor.yield sends a value to the main thread, and r.take receives it. The first r.take gets 10.

2. Step 2: Analyze second r.take call

   The block returns 20 after yield, which is the final value. The second r.take gets 20. After that, the Ractor is closed. A third r.take would cause error, but here only two calls are made, so no error.

3. Step 3: Check the code carefully

   Both r.take calls are valid; no error occurs.

4. Final Answer:

   No error, code runs fine -> Option C

5. Quick Check:

   Ractor.yield and take work twice safely [OK]

Hint: Ractor.yield sends values, take receives them sequentially [OK]

Common Mistakes:

• Thinking Ractor.yield is invalid inside Ractor
• Expecting error on second take call
• Assuming Ractor.new needs arguments

5. You want to sum numbers from 1 to 100 using two Ractors running in parallel, each summing half the range. Which code correctly implements this?

hard

A. r1 = Ractor.new { (1..100).sum }
r2 = Ractor.new { (1..100).sum }
puts r1.take + r2.take

B. r1 = Ractor.new { (1..50).sum }
r2 = Ractor.new { (51..100).sum }
puts r1.take + r2.take

C. r1 = Thread.new { (1..50).sum }
r2 = Thread.new { (51..100).sum }
puts r1.value + r2.value

D. r1 = Ractor.new { (1..50).reduce(:+) }
r2 = Ractor.new { (51..100).reduce(:+) }
puts r1.take * r2.take

Solution

1. Step 1: Split the range correctly

   We want two Ractors, one summing 1 to 50, the other 51 to 100.

2. Step 2: Check the operations and combining results

   r1 = Ractor.new { (1..50).sum } r2 = Ractor.new { (51..100).sum } puts r1.take + r2.take sums each half and adds results correctly. r1 = Ractor.new { (1..100).sum } r2 = Ractor.new { (1..100).sum } puts r1.take + r2.take sums full range twice (wrong). r1 = Thread.new { (1..50).sum } r2 = Thread.new { (51..100).sum } puts r1.value + r2.value uses Thread, not Ractor. r1 = Ractor.new { (1..50).reduce(:+) } r2 = Ractor.new { (51..100).reduce(:+) } puts r1.take * r2.take multiplies sums instead of adding.

3. Final Answer:

   r1 = Ractor.new { (1..50).sum } r2 = Ractor.new { (51..100).sum } puts r1.take + r2.take -> Option B

4. Quick Check:

   Split range, sum halves, add results [OK]

Hint: Split work, sum halves in Ractors, then add [OK]

Common Mistakes:

• Using Thread instead of Ractor
• Summing full range twice
• Multiplying sums instead of adding