Display server properties with SQL addon monitoring take a LOT OF TIME

Display server properties with SQL addon monitoring take a LOT OF TIME

Hi everybody,

We bought (and are still in test phase) the SQL monitoring add-on. And since i put the dashboard SQL on every SQL servers we have, then discovered every SQL instance and every DB attached to every instance. Now the opmanager website is lagging and sometimes freezing when (trying) display the server page.

My config : Virtual Server windows 2003 R2 x64, 4 vCPU, 8 Go RAM.

I have less than 500 devices and less than 500 interfaces monitored. and in the top of that,... the opmanager production server (which is still running on a windows 2003 R2 32bits,... less CPU and less RAM, BUT without addons... is more quick without any lags...)

I tried many changes in the wrapper.conf, tried to adapt the "startMySQL.bat", tried to update the values in the "my-huge.ini" file : no way.

In Process Explorer, the process mysqld-nt.exe cannot go over than 25% of CPU and it lags ONLY when i tried to display dashboard for AD, Exchange or SQL monitored servers.

anyway, is there a REAL best practice to "fine-thune" opmanager & mysql poor performance.... what is the difference (in wrapper.conf...) between "wrapper.java.initmemory" and "wrapper.java.maxmemory" and which value to put.

Also in wrapper.conf, what are wrapper.java.additional.10=-XX:PermSize=64m and wrapper.java.additional.11=-XX:MaxPermSize=128m ???

In every case is there a way to "calculate" or find the BEST config in many conf file to avoid lagging, freezings...


Thanks in advance.

Francky





















                  New to ADSelfService Plus?