Hacker News Reader

I'm real curious what kind of development you're doing with node.JS where Windows Defender causes trouble.

The real-time scanning slows down processes that access a large number of files, like code compiles in general and importing node modules in particular.

I haven't noticed Windows Defender causing significant slowdowns for processes which access lots of files except when it does a full system scan (which is not often). Even then, it's only barely noticeable.

I've disabled defender due to high CPU usage on machines that had to slice mpegs into jpegs with near constant work.

The machine was slicing up 11 channels of 24fps videos into jpegs, so 264 jpegs/s at 720p and 24 bit color.

I've had friends and coworkers that have hit the same CPU issues with big git repos and defender.

It seems like Defender has problems with getting hit with tons of small files in quick succession, but really I know very little about it.

Why not just exclude nodemodules folder and temp/cache? This helps me enough.

Reply on news.ycombinator.com