Re:Computing file hashes with node.js
by fexl on Tuesday November 01, 2011 @10:24AM
(#3182145)
I have noticed a popular aversion to "fork", and I don't quite understand it. It uses the "copy on write" technique, and it seems very fast in my benchmarks. For example, I have a benchmark where I can spawn 1000 or more processes right from the command line, all banging away on shared files with locking, and it all seems very fast and stable, every time. I don't even bother with pre-forking. But I do make heavy use of "Keep-Alive", with appropriate guards against abuse under heavy load. I'm a big fan of the simplicity of fork and blocking I/O, but I'm sure other people have different requirements and constraints they might want to share here.
[ Parent
| on HN ]
Re:Computing file hashes with node.js
by SaltwaterC on Tuesday November 01, 2011 @11:20AM
(#3182454)
Spawning a new process is not the same thing as forking, but people often forget this bit. This post wasn't about forking.
I thought that spawning a new process was the same as forking. What am I missing?
Re:Computing file hashes with node.js
by SaltwaterC on Tuesday November 01, 2011 @02:03PM
(#3183280)
http://linux.die.net/man/2/fork - this explains better.