Why concurrency matters in Ruby - Visual Breakdown

Concept Flow - Why concurrency matters in Ruby

Start Program

↓

Multiple Tasks?

Yes↓

Run Tasks Sequentially

→Slow Performance

↓

Use Concurrency

↓

Tasks Run Overlapping

↓

Better Performance & Responsiveness

↓

End Program

This flow shows that when a Ruby program has multiple tasks, running them one after another is slow. Using concurrency lets tasks overlap, making the program faster and more responsive.

Execution Sample

Ruby

threads = []
5.times do |i|
  threads << Thread.new { sleep(1); puts "Task #{i} done" }
end
threads.each(&:join)

This Ruby code runs 5 tasks concurrently using threads, each sleeping 1 second before printing a message.

Execution Table

Step	Action	Thread Created	Sleep Time	Output	Notes
1	Start loop i=0	Thread 0	1 sec		Thread 0 starts and sleeps
2	Start loop i=1	Thread 1	1 sec		Thread 1 starts and sleeps
3	Start loop i=2	Thread 2	1 sec		Thread 2 starts and sleeps
4	Start loop i=3	Thread 3	1 sec		Thread 3 starts and sleeps
5	Start loop i=4	Thread 4	1 sec		Thread 4 starts and sleeps
6	After ~1 sec sleep			Task 0 done	Thread 0 wakes and prints
7	After ~1 sec sleep			Task 1 done	Thread 1 wakes and prints
8	After ~1 sec sleep			Task 2 done	Thread 2 wakes and prints
9	After ~1 sec sleep			Task 3 done	Thread 3 wakes and prints
10	After ~1 sec sleep			Task 4 done	Thread 4 wakes and prints
11	Main thread joins all				Waits for all threads to finish
12	Program ends				All tasks done concurrently

💡 All threads complete after about 1 second, showing concurrency reduces total time.

Variable Tracker

Variable	Start	After Thread 0	After Thread 1	After Thread 2	After Thread 3	After Thread 4	Final
threads	[]	[Thread 0]	[Thread 0, Thread 1]	[Thread 0, Thread 1, Thread 2]	[Thread 0, Thread 1, Thread 2, Thread 3]	[Thread 0, Thread 1, Thread 2, Thread 3, Thread 4]	[Thread 0, Thread 1, Thread 2, Thread 3, Thread 4]

Key Moments - 2 Insights

Why do all tasks finish after about 1 second instead of 5 seconds?

Because threads run at the same time (concurrently), all tasks sleep simultaneously, so total time is about the longest single sleep (1 second), not the sum (5 seconds). See execution_table rows 6-10.

Does Ruby run threads in parallel on multiple CPU cores?

Ruby's standard threads run concurrently but not truly in parallel due to the Global Interpreter Lock (GIL). They switch quickly to give the appearance of parallelism, improving responsiveness. This is why concurrency still helps, even if not full parallelism.

Visual Quiz - 3 Questions

Look at the execution_table at step 5. How many threads have been created by then?

A 3

B 4

C 5

D 1

💡 Hint

Check the 'Thread Created' column up to step 5 in the execution_table.

At which step do threads start printing their output?

A Step 6

B Step 1

C Step 11

D Step 3

💡 Hint

Look for the first 'Output' value in the execution_table.

If we removed the 'threads.each(&:join)' line, what would happen?

A Program would wait for all threads to finish before ending.

B Program might end before threads finish printing.

C Threads would run sequentially.

D Threads would not be created.

💡 Hint

Refer to the 'Main thread joins all' note at step 11 in the execution_table.

Concept Snapshot

Concurrency in Ruby lets multiple tasks run overlapping in time.
Threads can sleep or work simultaneously, improving speed.
Ruby threads are concurrent, not fully parallel due to GIL.
Use threads and join to manage concurrent tasks.
Concurrency helps programs be faster and more responsive.

Full Transcript

This visual execution shows why concurrency matters in Ruby. When a program has multiple tasks, running them one after another takes longer. Using threads, Ruby can run tasks concurrently, overlapping their execution. The example code creates 5 threads, each sleeping 1 second then printing a message. The execution table shows all threads start quickly and sleep at the same time. After about 1 second, all threads wake and print their messages almost together. This means the total time is about 1 second, not 5 seconds if run sequentially. The variable tracker shows how the threads array grows as threads are created. Key moments explain why concurrency speeds up tasks and clarify Ruby's thread behavior with the Global Interpreter Lock. The quiz tests understanding of thread creation, output timing, and the importance of joining threads. The snapshot summarizes concurrency benefits and Ruby thread basics.