News for hackers. Stuff that matters.

A comment on Windows Subsystem for Linux Architectural Overview. Parent comment

Re:Windows Subsystem for Linux Architectural Overview by viraptor on Saturday April 23, 2016 @05:28AM (#11554833)
Does the fork performance really matter these days anymore? I mean comparing from one side to the speed of loading the app itself, fork is usually super cheap; on the other comparing to per-process async event handling, it's so slow pretty much nobody uses it this way for network apps anymore. What's the use case for a fast fork today?
[ Parent | on HN ]
Re:Windows Subsystem for Linux Architectural Overview by jibsen on Sunday April 24, 2016 @07:41AM (#11559352)
I don't know if it is due to various fork implementations being slow on Windows, but programs that spawn a lot of subprocesses like build tools can be really slow [1].

I would love to see some numbers for those from Bash on Windows.

[1]: https://gist.github.com/jibsen/7ebeddde3bc2bfd421b96ae53a824...

[ Parent | on HN ]
Re:Windows Subsystem for Linux Architectural Overview by ulber on Saturday April 23, 2016 @06:18AM (#11554939)
One example: The HyPer in-memory database from TUM uses fork to provide fast snapshots for running OLAP queries on fresh data.

[1]: http://hyper-db.de

[ Parent | on HN ]
Re:Windows Subsystem for Linux Architectural Overview by poooogles on Saturday April 23, 2016 @07:58AM (#11555182)
Redis uses fork to save to disk.
[ Parent | on HN ]
Re:Windows Subsystem for Linux Architectural Overview by viraptor on Saturday April 23, 2016 @08:03AM (#11555189)
Does fork on windows actually block parent for a long time, or does it only delay the child? I thought it was the latter, which shouldn't affect Redis. (but I may be wrong)
[ Parent | on HN ]