If the squirrels don’t gather enough supplies for a long winter, they will be out scampering in the snow and risk untoward dangers.Īnd so it is with our computer systems-they demand monitoring, planning, and preparation for contingencies.

If I don’t roll up hoses and bring them into the garage, pipes could freeze. If I don’t clean the leaf troughs in the early autumn, winter rains and subsequent freezing could spell disaster for the roof. And yet they demand a certain amount of preparation. Who knows, it may become really hot and humid over the weekend, but today I can delude myself into hearing the rustling of leaves, imagine cool breezes blowing across the yard, and think of squirrels as they quickly gather supplies for a long winter.Īll of these things are really quite simple, routine, and ordinary. This morning it is beginning to look like autumn. Microsoft Scripting Guy, Ed Wilson, is here. This way, the CPU is always doing something.Summary : Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell to monitor for the creation of specific processes. When the I/O is done, that process is moved back to the run queue. When a process on the run queue needs to do I/O, the OS puts it on another queue, and the CPU starts processing the next job. Nowadays, modern operating systems can run several processes at once and optimize CPU utilization. Because CPU speeds are so much faster than I/O speed, the machine would spend the majority of the time reading in the cards (I/O) while the CPU waited. Of course the major drawback of a Batch Monitor is that the CPU was often idle. The programmer would sit in front of a monitor, which would display memory dumps, debugging information, etc - it was an incredibly tedious process. You would 'program' the job onto punch cards and put them on an input queue that the machine would process one by one. In the 1950s - mid 60s, before we had true operating systems, we had Batch Monitors.

Monitor in this context means Batch Monitor.

Process monitor operating system