4 ms·

Copy on write fork mitigates some of that.

• squeaky-clean 4y ago
  There was a recent post about a new Ruby server implementation. The author pointed out that for interpreted languages, forking quickly deviates and gains very little benefit from copy-on-write. However! Pre-warming the first instance and then forking afterwards brought the memory savings back down to compiled levels. No real point to my comment except that it was new knowledge to me, and that efficiency of forking really depends on the implementation of what/when you're forking.
• m00x 4y ago
  It's not clear what OP is saying. I assumed multiple container instances, but even then, CoW isn't as efficient.