Memory_TopConsumers

[Former Member]

Hi,

Due to performance issues on our present situation in landscape I have checked SQL HANA_Memory_TopConsumers . I see result

MEMORY_REDUCTION_APPROACHES as Application data management and archiving .

Can anyone suggest on Application data management and archiving mean here ,Is it partioing date. Any procedure to follow to ? Also suggestion require on heap area and row store.

fyi..

30003    indexserver    Column store    EKPO    15.14    3.75

61.33    Size of table EKPO in column store    Application data management and archiving

30003    indexserver    Column store    /POSDW/TLOGF    13.11    3.24        71.69    Size of table /POSDW/TLOGF in column store    Application data management and archiving

30003    indexserver    Column store    /POSDW/PLOG1S    12.11    2.99        74.68    Size of table /POSDW/PLOG1S in column store    Application data management and archiving

***********

	PORT	SERVICE	AREA	DETAIL	SIZE_GB	SIZE_PCT	CUM_SIZE_PCT	DESCRIPTION	MEMORY_REDUCTION_APPROACHES
1	30003	indexserver	Heap area	Pool/malloc/libhdbcsmd.so	34,86	8,63	8.63	Column store	Cleanup, compression and archiving of column store tables
2	30003	indexserver	Heap area	Pool/ColumnStoreTables/Main/Dictionary/RoDict	28,66	7,09	15.73
3	30003	indexserver	Heap area	Pool/PersistenceManager/PersistentSpace(0)/DefaultLPA/Page	27,93	6,91	22.64	Page cache	Space is automatically reclaimed if required
4	30003	indexserver	Heap area	Pool/malloc/libhdbcsapi.so	24,81	6,14	28.79	Column store	Cleanup, compression and archiving of column store tables
5	30003	indexserver	Heap area	Pool/RowEngine/SQLPlan	23,09	5,71	34.51	SQL cache	See SAP Note 2124112
6	30003	indexserver	Heap area	Pool/RowEngine/SQLPlan	22,79	5,64	40.15	SQL cache	See SAP Note 2124112
7	30003	indexserver	Heap area	Pool/ColumnStoreTables/Main/Compressed/Indirect	19,82	4,9	45.06
8	30003	indexserver	Column store	VBUP	19,06	4,72	49.78	Size of table VBUP in column store	Application data management and archiving
9	30003	indexserver	Heap area	Pool/Statistics	16	3,96	53.75	Internal statistical information	Open SAP incident in case of very large and rising size
10	30003	indexserver	Heap area	Pool/ColumnStoreTables/Main/Uncompressed	15,47	3,83	57.58
11	30003	indexserver	Column store	EKPO	15,14	3,75	61.33	Size of table EKPO in column store	Application data management and archiving
12	30003	indexserver	Heap area	Pool/ColumnStoreTables/Main/Rowid	14,9	3,69	65.02
13	30003	indexserver	Heap area	Pool/Statistics	13,8	3,41	68.44	Internal statistical information	Open SAP incident in case of very large and rising size
14	30003	indexserver	Column store	/POSDW/TLOGF	13,11	3,24	71.69	Size of table /POSDW/TLOGF in column store	Application data management and archiving
15	30003	indexserver	Column store	/POSDW/PLOG1S	12,11	2,99	74.68	Size of table /POSDW/PLOG1S in column store	Application data management and archiving
16	30003	indexserver	Heap area	Pool/ColumnStoreTables/Main/Index/Single	10,84	2,68	77.37
17	30003	indexserver	Heap area	Pool/malloc/libhdbcstypes.so	9,38	2,32	79.69	Column store	Cleanup, compression and archiving of column store tables
18	30003	indexserver	Column store	EDID4	9,38	2,32	82.02	Size of table EDID4 in column store	SAP Note 706478 (archiving and cleanup options)
19	30003	indexserver	Column store	/POSDW/AGGRTI	7,31	1,81	83.83	Size of table /POSDW/AGGRTI in column store	Application data management and archiving
20	30003	indexserver	Row store	Row store fragmentation	6,8	1,68	85.51	Row store fragmentation	See SAP Note 1813245 and reorganize row store

Regards,

DK

[former_member183326]

When you say you had performance issues, can be elaborate more on this? Checking your memory wouldn't be the best way of troubleshooting this. Are you seeing high cpu, hanging, slow runtimes? Have you tried running some runtime dumps during the performance issues to see which SQL's are running at that time? I don't see anything wrong with the memory alllocators you have posted either. What revision are you running?

[Former Member]

Hi Michael,

Rev 102.06.Performance issue is a part that customer wants to check. During issues we checked SQL memory top consumers. For the moment I am trying to check  - Application data management and archiving mean on Column store . How can we on perform on tables like EKPO, /POSDW/TLOGF,/POSDW/PLOG1S.

Regards,

DK

[former_member183326]

Again, can you explain the issue? This will help me to understand more. Why are you checking the memory during the issue? What prompted you to think to look this direction? What exactly would you like to perform for Column store tables?

[Former Member]

I am trying to reduce maximum possibilities that be related to memory.  MEMORY_REDUCTION_APPROACHES is the possible way I see from Memory top consumers.

I would like to perform and understand how can  Application data management and archiving mean on Column store.

[former_member183326]

I would first start off by looking here Note 1999997

9. Which options exist to reduce the risk of SAP HANA memory issues?

In my experience what you are trying to do is most likely not going to improve any performance issues you are seeing. Are you getting OOM dumps in your system? I am still trying to find out the actual performance issue you are having?

Make sure your HugePages are also turned off

[Former Member]

We dont have OOM dumps for now. As i said performance issue is a part while checking top memory consumers  I am trying to understand how we can perform Application data management and archiving on Column store

I believe same as most likely not going to improve any performance issues but top memory consumers were the finding and may be if demanded we may have to apply Application data management and archiving on Column store. So question is on Application data management and archiving on Column store rather than performance issue.