← Graph

Global Interpreter Lock

concept 5 connections

MRI Ruby's GIL, together with suboptimal Matz-Ruby-Moritomo concurrency internals, limits Ruby's suitability for concurrent workloads like WebSocket servers. Cited as the core reason Ruby struggles with real-time broadcast latency at scale.

category
architecture
talk How (and why) to run SQLite in production
about
Global Interpreter Lock concept
Core reason SQLite's native busy_timeout harms Rails concurrency — it holds the GVL.
takeaway Replace SQLite's C busy_timeout with a GVL-releasing Ruby handler
about
Global Interpreter Lock concept
The point of the fix is to release the GVL during DB waits.
talk One machine please, make it Turing
about
Global Interpreter Lock concept
Halasz notes the GVL that 'kills parallelism in Ruby' lives inside the virtual machine layer.
tool Action Cable
related_to
Global Interpreter Lock concept
Cited as a root cause of Action Cable's concurrency limits.
concept SQLite Busy Handler
related_to
Global Interpreter Lock concept
The native C busy_timeout holds Ruby's GVL; the Ruby re-implementation releases it via Kernel#sleep.

Provenance

Created in
Cables! Cables! Cables! — Vladimir Dementyev at wroclove.... 2026-04-17 16:18
Read by
20 extractions