Skip to Content
avatar image
Former Member

Memory_TopConsumers

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

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Aug 06, 2016 at 09:55 PM

    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?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Michael Healy

      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.