Apa iku GVL lan kepriyee cara concurrency mungo ing Ruby?

Question

Accepted Answer

**GVL** (Global VM Lock, biyen GIL) ing MRI Ruby mung ngidini **siji thread nglaksanakake Ruby code ing wektu kang padha** — dadi thread ora nyedhiyakake parallelism CPU sing sejati. Nanging GVL iku **dirilis sajrone I/O**, dadi thread *bener* mbantu kanggo I/O-bound work. Kanggo parallelism CPU, sampeyan nggunakake multiple processes. Iki mirroring situasi GIL Python.

## GVL: siji thread nglaksanakake Ruby code ing wektu kang padha

```text
MRI (the standard Ruby) has a GLOBAL VM LOCK:
  → only ONE thread executes Ruby code at any instant (no CPU parallelism from threads)
  → BUT the GVL is RELEASED during blocking I/O (network, file, DB)
So: threads help for I/O-bound work, NOT for CPU-bound work.
```

## Threads — apik kanggo I/O-bound concurrency

```ruby
# ✅ I/O-bound — threads overlap waiting (GVL released during I/O) → real benefit
threads = urls.map do |url|
  Thread.new { fetch(url) }      # while one waits on the network, others proceed
end
threads.each(&:join)

# ❌ CPU-bound — threads do NOT speed this up (GVL serializes Ruby execution)
threads = data.map { |d| Thread.new { heavy_computation(d) } }  # no speedup
```

Thread mbantu kanggo I/O-bound work (network, file, DB) amarga GVL dirilis sajrone panggunggang, ngidini thread liyane mlaku. Iku *ora* nyepetake CPU-bound work (GVL serializes Ruby execution).

## Processes — kanggo CPU-bound parallelism

```ruby
# ✅ CPU-bound parallelism → use multiple PROCESSES (each has its own GVL)
# fork, or gems like Parallel:
results = Parallel.map(data, in_processes: 4) { |d| heavy_computation(d) }
# → 4 separate processes, true parallelism across cores
```

Kanggo CPU-bound parallelism, gunakake **multiple processes** (saben-saben kalawan GVL/interpreter dhewe) — `fork`, `parallel` gem, utawa nglaksanakake multiple worker processes (cara Rails servers kaya Puma scale).

## Modern concurrency tools

```text
✓ Ractors (Ruby 3) — actor-model parallelism that CAN run Ruby in parallel (no shared GVL
  per Ractor) — experimental, true parallelism
✓ Fibers / async gem — lightweight cooperative concurrency for high-I/O workloads
✓ Background jobs (Sidekiq) — offload work to separate worker processes
Note: alternative Ruby implementations (JRuby, TruffleRuby) have NO GVL → true thread parallelism
```

## Apa iki penting

Ngerteni GVL lan Ruby concurrency iku penting — lan asring disalaherteni — ilmu kanggo nggawe Ruby applications sing performant, kaya situasi GIL Python.

Insight kunci iku MRI Ruby **GVL mung ngidini siji thread nglaksanakake Ruby code ing wektu kang padha**, dadi thread ora nyedhiyakake CPU parallelism — titik bingung sing umum.

Kritisne, GVL iku **dirilis sajrone I/O**, iki tegese pendekatan concurrency sing tepat gumantung ing workload: **threads kerja apik kanggo I/O-bound tasks** (network calls, file/database access — ngendi GVL dirilis sajrone panggunggang, ngidini thread tumpang tindih), nanging **CPU-bound parallelism perlu multiple processes** (saben-saben kalawan GVL dhewe, nggawe parallelism sejati lanang cores — liwat `fork`, `parallel` gem, utawa multiple worker processes, iki cara Rails servers scale).

Salaherteni GVL ndadekake code concurrency sing ora efektif (contohe gunakake threads kanggo CPU-heavy work ngandharep speedup).

Ngerti keputusan I/O-vs-CPU (threads kanggo I/O concurrency, processes kanggo CPU parallelism), modern tools (Ractors kanggo experimental true parallelism, Fibers/async kanggo high-I/O cooperative concurrency, background job processors kaya Sidekiq), lan yen alternative implementations (JRuby, TruffleRuby) ora duwe GVL iku penting kanggo nulis concurrent Ruby sing bener-bener performant.

Yamarga concurrency iku kebutuhan umum lan GVL fundamentally nggawekake pendekatan yang tepat, ngerti iku — kepriyee threads ora parallelize CPU work, yen iku mbantu kanggo I/O, lan processes perlu kanggo CPU parallelism — iku penting senior-level knowledge sing nyegah kesalahan sing asring lan topik interview umum sing ngreflekseni ngerti Ruby concurrency model lan GVL constraint-ne.