cancel
Showing results for 
Search instead for 
Did you mean: 

liveCache sizing

Former Member
0 Kudos

Hi All

We had few performance issues in production box and after checks found that data area usage in LC was very high at 90% ,during peak load.

So we have added 4gb (  two new data files of MAXDB ), now the system performance looks better and data area utilization of max db is about 72%.

Currently we have 30GB RAM ( memory ) in LC and 52 GB data files of MaxDB .Out of 52 GB , we have 14GB as free space.

Is there any simple ratio or thumb rule for MAXDB disc space to physical Memory

Do we  have to increase the physical memory (RAM) in LLC

Radhakrishnan

Accepted Solutions (1)

Accepted Solutions (1)

former_member188883
Active Contributor
0 Kudos

Hi Radhakrishnan,

Please evalaute your MaxDB configuration as per SAP recommendation. Post this you may look for enhancement of physical hardware resources.

Refer below SAP notes for suggestions

Note 719652 - Setting initial parameters for liveCache 7.5, 7.6, 7.7

Note 487972 - Operating system parameterization of liveCache

Hope this helps.

Regards,

Deepak Kori

former_member229109
Active Contributor
0 Kudos

Hello Radhakrishnan,

1.

During the high loading in parallel the luck of CPU, memory and locking issues could occur, which leaded to the long running liveCache transactions, many history pages created.

After the transactions finished or canceled, the consistent views in liveCache were released/flaged for deletion & deleted by Garbage collectors, which run regularly.

Use the DB analyzer to find the bottleneck in liveCache.

Create the SAP message to SV-BO-SCM component to check & help you with performance tunning of the load to liveCache scenario.

2.

Please review the SAP note:

1247666 FAQ: SAP MaxDB/liveCache history pages

Regards, Natalia Khlopina

Answers (1)

Answers (1)

Former Member
0 Kudos

Thanks all , we will check with  our Basis team