Solution Manager use High Memory

[Former Member]

Hi,

I am facing problem after installation of Solution Manager 4.0.its take virtual memory utilization about more then 4.5 GB.Data Base used as SQL Server 2005.

Please help me to troubleshoot this problem.

Regards

Gyan

[Former Member · Accepted solution]

Hello Gyan,

There are times when paging will seem high even though the memory

is not totally used.

If you are just getting large page outs then it is no big deal for NT,

it is probably is lazy paging (covered in the online help)

If you are getting large page ins then it is just that users are

re-using memory that has been paged due to one of a myriad of reasons.

If you are getting page-over the 20% of the RAM you can check what is

going on:

If RAM is totally ocupied, than a real memory bottleneck is very

probable. A further sign for a memory bottleneck can be high CPU

consumption during high paging phases, because the CPU is occupied by

swapping out the memory.

When you can exclude a real memory bottleneck, you should

check, which processes are active at this moment and causing the

paging by I/O. Examples for processes causing high I/O:

- Online backup (database server9

- Dr. Watson scanning the disks

- computer viruses ....

Note 313347, which explains the limits of allocation can be reviewed.

Since this has got more to do with the SQL server consuming memory. You can also refer this issue to Microsoft.

Regards

Amit

[Former Member]

Hello Gyan,

There can be a good number of reasons for this High Memory Usage that you have quoted.

Firstly Have you installed Solution Manager along with the Java Services. If yes then it is quite obvious that your JVM and other services are taking a good amount of share out the memory available.

The reason for the high memory consumption is can be the solutions that you have maintained.A solution is meant to be a set of systems that are sharing a

business process. In our sizing guideline we recommend that

the number of alerts per solution should not exceed 500 (if the

monitoring scenario is going to be used).

The architecture of the framework that is used for the Setup System

Monitoring makes is necessary to build up these huge internal tables.

A reduction of the size of the internal tables could be only

achieved by switching off some funtionality (in this case it would be

the value helps for the 'Copy Customizing' function).

Thirdly it can also be the case that your Memory storage parameters are set wrongly. Check them once with the standard recommendations for them.

Ideally if you are running Solution Manager on NT you can use the Zero Memory administration feature.

Hope that the above information gives you an clue on your issue.

Regards

Amit

[Former Member]

Dear Amit,

Thanks for information sharing.But SQL Server process take heavy memory utilization and Solution manager not configured yet.

Regards

Gyan