My services.exe process was consuming a lot of CPU resources this morning, for no apparent reason.

If I examined this process, I saw that it had created three different threads that were equally busy in working on some unspecified task. No I/O performed, no network activity, just a lot of CPU resources on three different threads.

In Linux, this would have been less of a problem, because in Linux, each process is designed to perform one single job, and do it well. When task A needs to be executed, /usr/bin/taska is started. When task B a little later needs to be carried out, /usr/bin/taskb is run. But in Windows, one process can host a vast multiple jobs, and frequently, a number of different roles are included in one single application. Of course, since process creation is an expensive task in Windows, it makes sense to use threads instead. But you lose out on clarity.

Well, I don’t know why my computer disbehaves like this. I guess I’ll go over it with my antivirus utility and then reboot, to see if the problem goes away. That’s about all I can do.