Why are WMI Queries so slow sometimes?

c# wmi
Josh Clark picture Josh Clark · Sep 14, 2009 · Viewed 11.5k times · Source

I am using System.Management namespace in a .Net to execute various WMI queries against a remote server. In my logs I can see that sometimes the queries take 30 or 40 seconds to complete while other times the queries complete in less than a second.

When I see these slow queries, I try to connect to the box using wbemtest, but it always connects and executes the query quickly.

Any ideas, pointers, suggestions?

I did notice when looking at System.Management.ManagementScope in reflector that it seems to leak a IWbemServices pointer. It looks like this is a COM Interface that needs to have Release called on it (Marshal.ReleaseComObject()). I'm not sure if that is related or not. I do connect to lots of different servers during the life of the process.

Answer

SwDevMan81 picture SwDevMan81 · Sep 15, 2009

You could try and set the WITHIN field to see if it forces the query to happen sooner. Could you post the query you are using? That might help debug any further issues

Related questions

How to solve '...is a 'type', which is not valid in the given context'? (C#)

The following code produces the error: Error : 'CERas.CERAS' is a 'type', which is not valid in the given context Why does this error occur? using System.Drawing; using System.Linq; using System.Text; using System.Windows.Forms; namespace WinApp_…

Read More
How to get CPU temperature?

I need to gather some system's information for the application I'm developing. The memory available and the CPU load are easy to get using C#. Unfortunately, the CPU temperature it's not that easy. I have tried using WMI but I …

Read More
Detecting USB drive insertion and removal using windows service and c#

Looking into possibility of making an USB distributed application that will autostart on insertion of an USB stick and shutdown when removing the stick Will use .Net and C#. Looking for suggestion how to approach this using C#? Update: Two …

Read More