News for hackers. Stuff that matters.

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

Re:A fork() in the road by waterhouse on Wednesday April 10, 2019 @05:14AM (#19623027)
The last time I used WSL (perhaps 6 months ago), its per-process overhead was awful. I don't recall the numbers, but I think it managed to start fewer than 10 processes per second. My memory suggests it was more like two processes per second, though I would recommend re-testing before trusting that.

Found my previous comment on it (which has a test case but not numbers): https://news.ycombinator.com/item?id=18226921

[ Parent | on HN ]
Re:A fork() in the road by temac on Wednesday April 10, 2019 @09:29AM (#19624411)
On 1803 and 1903 it's 3 to 4 times faster than MsysGit (WSL is ~1s on my laptops). It is possibly slightly faster on 1903 as my laptop running it is faster than the other for this bench, despite having an older processor.

Now in a Linux VM it's approx 10 times faster than even WSL. And that should probably be even faster natively.

So anyway WSL is really usable and if you really only started 10 processes per sec something is wrong. Maybe you are using a crappy antivirus (I've heard that Kaspersky makes WSL extremely slow)

[ Parent | on HN ]
Re:A fork() in the road by waterhouse on Wednesday April 10, 2019 @03:29PM (#19627972)
Well, I hadn't installed any antiviruses myself. I think Windows Defender was running, though. It's possible that my computer came with additional crapware on it.
[ Parent | on HN ]
Re:A fork() in the road by temac on Wednesday April 10, 2019 @03:48PM (#19628139)
I just checked and both of my benchs were done with Defender.

When I disable it, it is down to ~0.5s

I would not build a Linux kernel here instead of in a VM, but for tons of things, this is very usable.

[ Parent | on HN ]