> The problem with the strategy was that it required a lot of CPU and RAM to sta... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

saagarjha on Feb 22, 2020 | parent | context | favorite | on: Does memory leak? (1995)

> The problem with the strategy was that it required a lot of CPU and RAM to startup a new process.

It's not really kosher, but why not just keep around a fresh process that they can continually fork new handlers from?

Filligree on Feb 22, 2020 [–]

Setting it up was expensive, so there's a good chance it involved initializing libraries, launching threads, or otherwise creating state that isn't handled correctly by fork.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact