em/initial_size_MB / Physical RAM

[Former Member]

Hello,

I have a client who is experiencing some performance issues so I'm just reviewing the memory parameters/allocations.

Environment is Windows/SQL.

The box has 8GB of physical memory with 24GB of virtual memory.

em/initial_size_MB is set to 10GB.

I have in the back of my mind that em/initial_size_MB should not be greater than the amount of physical memory.  Is that correct? And if it's set to a higher value, what issues could it cause?

Many thanks.

[Former Member · Accepted solution]

Hi Paul ,

Check the below sap note

88416 - Zero administration memory management for the ABAP server

The parameter above has some limitation for kernel as well.

For the same checked the sapnote

1458065 - Extended memory restricted to 64G

835474 - More than 32 GB extended memory

With Regards

Ashutosh Chaturvedi

[Former Member · Accepted solution]

Thanks for the suggestions.

So note 88416 suggests that em/initial_size_MB should be equal to PHYS_MEMSIZE??

PHYS_MEMSIZE does not exist in this particular system. 

Presumably it will just be the value of the of the amount of RAM in the box?

In which, I need to be reducing em/initial_size_MB to 8GB?

[Former Member · Accepted solution]

Hi Paul,

Whats your kernel version?

With Regards

Ashutosh

[Former Member · Accepted solution]

721 EXT Unicode - Patch Level 201

[Former Member · Accepted solution]

Hi Paul,

Then Zero administartion sapnote fits the kernel requirement.

You can wait for others to reply on your thread to have a good picture of the parameters.

With Regards

Ashutosh Chaturvedi

[Reagan · Accepted solution]

The SAP note 88416 - Zero administration memory management for the ABAP server suggested by Ashutosh is the answer. If the parameter PHYS_MEMSIZE is not set then you should set it.

1926986 - Best practice formulas in profile maintenance

RB

[S_Sriram · Accepted solution]

Hi Paul

As per the SAP stranded you have to set the memory 70% Application & 30% Database.

1. In your MS SQL server memory resource should not cross more than 30 % of memory? If it is yes, you can set the memory parameters in MS SQL MMC

2. Balance amount 70% of memory can be used for application & OS

3. You can restart the system check the transaction code ST02 memory & buffer usage Is this any swaps?

4. Check the DB over all usage? refer the SCN link how you can fine trun the DB?

Regards

Sriram