3 ms·
It's only one core pegged at 100%, practically nothing else, which means it's a sequential workload entirely blocked on defender.
by the8472 7y ago
It's only one core pegged at 100%, practically nothing else, which means it's a sequential workload entirely blocked on defender.
- BlueTemplar 7y agoOh, you mean that Defender locks your thread?
- the8472 7y agoI don't recall seeing significant locking in the stack samples, just that the scanning happens synchronously during some IO (e.g. closing file handles) and >90% of the CPU cycles are spent on defender. Which effectively boils down to a task that should be IO-bound becoming bottlenecked by waiting on defender.