I have a discovery that runs a Datasource VBScript and it returns about 65 or so class instances (with three properties each), 65 or so relationship instances, all using addProperty and addInstance and at the end doing the ReturnItems. The current discovery is taking over 5 hours to complete and is running on the RMS (It has to for now). The RMS is a 12core physical server with over 40gb of RAM. When running this script locally on my laptop via Simulation in the Authoring Console, I noticed that MonitoringHost.exe topped out at 25% of my CPU. It's a 4core laptop. Is MonitoringHost.exe able to utilize multiple cores???? It appears to be the same problem on the RMS. It tops out at 8% on 12 Cores and is running all of the time because of it. I currently am in need of discovering approximately 20 more classes with properties and raltionships but really really not looking forward to adding another hour to the discovery time. When we add new infrastructure to our App, we need it monitored RIGHT AWAY. I get dirty looks from people when I say it'll take 5+ hours. :(

Does the script actually run for that long? Consider tuning the script for better performance, and maybe cascading the discovery into multiple, shorter runs as to not create such a load all at once.HTH, Jonathan Almquist - MSFT

No, the script runs in 3 seconds or so. I ran it via cmdline and saw the output. It's the processing after the data items are returned. The script would be running as a cscript.exe process. I found a way to fix my overall problem but the question still remains. What is restricting MonitoringHost.exe to only using 1 core in a multi-core system?

Hi, you could report that, around the multi CPU usage, on the connect website, connect.microsoft.com , as a feature request or bug. But running a 5 hours discovery on your RMS dosent sounds like a great solution. As Jonathan is writting, see if you can tune it in any way.Anders Bengtsson | Microsoft PFE | blog at http://www.contoso.se