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.

[Michel van Verk]

I had this issue as well. Enormous CPU utilization and memory leaks. mxdomainmgr used to use up to 1.2 GB on a 1 GB/2.4 Ghz system and utilization usually between 60-100%. I tended to change the process priority setting to low, that gave some relief. What often happened is that the mxdomainmgr process crashed probably and restarted because it used to drop suddenly to 40MB and the low priority settings of the process changed back to the default normal setting. CPU utilization remained high with the newly started process. I was monitoring only 6 machines at that time. Response of the HTTP server was extremely slow, it could take 5 minutes before the login prompt appeared.

I have reinstalled this system with the same OS (W2003), reinstalled the HPSIM 4.1 and now the system is running fine. Monitoring 70 devices, using 150MB memory and occasional high CPU load.

The difference between this installation and the one with high CPU load is that I have the SQL database on a seperate machine now. It is well worth a try to put your database on a seperate box.

Michel

[Tim McGue]

Michel,

Thanks for the additional information. When the 4.0 -> 4.1 migration is possible I will give that a try and explore setting up the SQL DB on a different server.

Tim