The Limits of Copy-on-write: How Ruby Allocates Memory
Anyone who’s run Unicorn (or Puma, or Einhorn) may have noticed a curious phenomena. Worker processes that have been forked from a master start with low memory usage, but before too long will bloat to a similar size as their parent. In a big production installation, each worker can be 100s of MBs or more, and before long memory is far and away the most constrained resource on servers. CPUs sit idle.
The Limits of Copy-on-write: How Ruby Allocates Memory #ruby #rubydeveloper #rubyonrails https://rubyonrails.ba/single/the-limits-of-copy-on-write-how-ruby-allocates-memory
Nezir Zahirovic
Contractor Ruby On Rails (8+ years) / MCPD .Net / C# / Asp.Net / CSS / SQL / (11 years)
