News for hackers. Stuff that matters.

A comment on A fork() in the road. Parent comment

Re:A fork() in the road by cryptonector on Wednesday April 10, 2019 @10:55AM (#19625287)
Yeah, it's not really cheap at all. However! vfork() is cheap, very very cheap, though, of course, you then have to follow it up with an exec(), and the cost of that on Windows depends on the setup cost of the executable being exec'ed.

Part of the problem is the DLLs, as many have mentioned, and also the fact that each statically links in its own CRT (C run-time). The shared C run-time MSFT is working on should help here. As should more lazy loading and setup.

[ Parent | on HN ]
Re:A fork() in the road by dblohm7 on Wednesday April 10, 2019 @04:04PM (#19628270)
> Part of the problem is the DLLs, as many have mentioned, and also the fact that each statically links in its own CRT (C run-time)

No, that isn't the case on DLLs shipped with Windows.

[ Parent | on HN ]
Re:A fork() in the road by cryptonector on Wednesday April 10, 2019 @04:29PM (#19628485)
But it is for 3rd party DLLs.
[ Parent | on HN ]
Re:A fork() in the road by dblohm7 on Thursday April 11, 2019 @12:30PM (#19636293)
Well, that depends on the DLL.
[ Parent | on HN ]