Why we switched from Python to Go

Re:Why we switched from Python to Go by tychver on Thursday October 19, 2017 @11:30AM (#15508740)

Forking 10 processes does not use 10x the memory of a single process starting 10 threads. It's actually almost identical. Both are implemented by the kernel using clone(). Many older tools written in "fast" languages like PostgreSQL and Apache also use forking.

[ Parent | on HN ]

Re:Why we switched from Python to Go by hasenj on Friday October 20, 2017 @12:58AM (#15513623)

We're not talking about forking here. Python/Ruby apps are actually spawned as several separate processes.

[ Parent | on HN ]

Re:Why we switched from Python to Go by tychver on Friday October 20, 2017 @05:15AM (#15514492)

Not for almost a decade. Ruby web servers and job processing frameworks have used forking out of the box since the release of Phusion Passanger 2 in 2008 and Resque in 2009.

[ Parent | on HN ]