Why does running a few instances of DIR /s in Command prompt load CPU heavily?
jacquesm: That's because you are the only user on the system and you're asking the filesystem to tell you everything it knows about all your files.Strictly speaking it is an io-bound operation, but with the number of files on your machine and some aggressive caching it will quickly turn into a memory-to-display translation (involving lots of font rendering and scrolling) and that is cpu-bound, not io-bound.Look at it this way, the 'idle' process also consumes lots of cpu power, but it does absolutely nothing. When you're alone on a machine you have the power to max it out with anything cpu bound, no matter how simple. A loop that counts from 0 to 1.000.000.000 (assuming it's not optimized out) will consume 100% cpu time unless you tell your system explicitly otherwise.The only way to not max out the cpu is to deliberately slow the process down by installing small sleep periods in between operations, but you really want your 'dir /s' to run as fast as it can.