Many IT departments run long running and intensive processes on the various PCs throughout their organizations. For example, virus scanners (are evil but that's another rant), defragmentation and disk cleanup stuff. Is it really too much to ask for them to put such background tasks in the LOW PRIORITY QUEUE!!!. Do they know what the low priority queue even is or that it exists? I have yet to see anybody, other than myself, think ahead far enough to say "Gee this would interrupt interactive performance. I know! I'll put this in the low priority queue instead of being rude". I wonder what the thought process is for the IT guys or even if there is a thought process...
And then processes spawned from the original process go in the normal queue, so even if you put the first process in the low queue, the next process pops out in the normal queue. The correct way to do this is to have the original process, the parent process, in the low queue and have it insure any children created are also in the low queue!
And then processes spawned from the original process go in the normal queue, so even if you put the first process in the low queue, the next process pops out in the normal queue. The correct way to do this is to have the original process, the parent process, in the low queue and have it insure any children created are also in the low queue!
No comments:
Post a Comment