mxdomainmgr.exe CPU utilization

[Tim McGue]

I see mxdomainmgr.exe continue to use 30-50% CPU utilization on an ongoing basis. Are others seeing this too? Is this expected?

[Rob Buxton]

I've seen it use 100% but usually when the Discovery task is running.

Normally CPU Usage is quite low.

You might want to see if there are any tasks running during these periods.

[Tim McGue]

I've checked for anything in the scheduled tasks and nothing shows as running while the CPU is high.

Furthermore, there is another post about a memory leak. I've watched the same process and over the past 3 hours is has gone from 448,000K memory usage to 980,000K.

Tim

[Arjen Dragt]

I saw this when I had HP SIM installed on too low-powered a box.

I moved it to a new DL380 and it is close to sleeping...

What hardware are you running this on?

[Jadrice Toussaint]

This post to confirm my findings. After conitnous stress testing and data gathering, I did not find any proof of memory leak with the mxdomainmgr.exe. The process when no polling and other related tasks are running, idles at 140MB of memory.

[Tim McGue]

Hardware configuration:
DL380 G3
4 Procs - 2 at 2.4 GHz, 2 at 500 MHz
4 GIG of memory

Current memory consumption of mxdomainmgr.exe:
1.5 GIG

CPU utilization is better now. It is under 10% (but I can't confirm the SIM is actually functioning now).

Tim

[Rob Buxton]

Tim,

How many devices are you monitoring?

[Tim McGue]

I have about 200 total systems with about 150 of those being servers.

[Rob Buxton]

I'm only monitoring about 130, of which only about 80 have Agents on them.
I've got HPSIM on an ML370 G2 with 1GB of memory.
The database is on a separate server.

The number of devices you're monitoring isn't particularly high, odd that there should be a big difference in resource usage.

Just watching ours now and it's using between 20-40% CPU and 205 K of memory, but it is also running the Software Polling task.

[Steven Kaufer]

I have noticed this happen on my system as well. I'm also running it on a DL380 G3. This tends to happen when there is a discovery running on the SIM.