A great summation of the ITMU/WU problem

David Gayler sent me this today, and it’s probably the best explanation of the ITMU/WU problem — showing that this is not directly an SMS issue, but a technology-wide WU problem.

=================

I have a question/observation. I have always noticed that the WU agent is EXTREMLY CPU intensive while performing a scan (online or offline). I suppose this new issue makes it worse, however if I perform a scan (using the WU COM API), the CPU will peg for over 1 minute when. Also, the filter criteria you can pass to the search interfaces seem to have little effect on this. IOW, even if I only ask for specific type of updates to be scanned for, it appears the engine does a full search (expensive from a CPU perspective) and then filters AFTER the scan. It doesn’t appear the scan engine understands how to take shortcuts on what to scan. Does this jive with what you have experienced in the past?

=================