This service appears to perform a large number of I/O requests (probably reading/writing a large number of small files). It will totally consume the disk seek capacity, massively slowing down every other program that is also doing disk I/O (e.g., freezing Firefox awesomebar searches).
The programmers at the linked blog congratulate themselves on how this mayhem lasts only 10 minutes on a typical computer.
Note: I do not have an SSD. :( This and other idiocies will force me to get one next time.
Fair enough. This occurs roughly once in two months when I least expect it.
But the point is that with just a bit more attention to detail, they could have made this process utterly unobtrusive: don't process more than once file per second, if you want want to build in heuristics to infer the disk seek bandwidth.
Btw, Microsoft Security Essentials may be doing things like this. For me, it is totally not noticeable.
I don't think it will be too long before every PC or laptop ships with an SSD as standard and mechanical disks will be relegated primarily to archiving duties.
https://blogs.msdn.com/b/davidnotario/archive/2005/04/27/412...
This service appears to perform a large number of I/O requests (probably reading/writing a large number of small files). It will totally consume the disk seek capacity, massively slowing down every other program that is also doing disk I/O (e.g., freezing Firefox awesomebar searches).
The programmers at the linked blog congratulate themselves on how this mayhem lasts only 10 minutes on a typical computer.
Note: I do not have an SSD. :( This and other idiocies will force me to get one next time.