Skip to content

ABAP Keyword Documentation →  ABAP - Reference →  Declarations →  Declaration Statements →  Data Types and Data Objects →  Types and Objects - Overview →  Data Objects →  Memory Management of Deep Objects 

Deep Data Objects, Memory Consumption

The example illustrates the management costs of deep components with low data content.

Other versions: 7.31 | 7.40 | 7.54

Source Code


    DATA: itab TYPE TABLE OF i,
          dref TYPE REF   TO i,
          rtab TYPE TABLE OF REF TO i,
          ltab TYPE TABLE OF i,
          ttab LIKE TABLE OF ltab,
          oref TYPE REF   TO lcl,
          otab TYPE TABLE OF REF TO lcl.

    FIELD-SYMBOLS <line> TYPE any.

    DO n TIMES.

      APPEND sy-index TO itab.

      CLEAR dref.
      CREATE DATA dref.
      dref->* = sy-index.
      APPEND dref TO rtab.

      CLEAR ltab.
      APPEND sy-index TO ltab.
      APPEND ltab TO ttab.

      CLEAR oref.
      CREATE OBJECT oref.
      APPEND sy-index TO oref->atab.
      APPEND oref TO otab.


    BREAK-POINT ##no_break.

    LOOP AT itab ASSIGNING <line>.
      FREE <line>.

    LOOP AT rtab ASSIGNING <line>.
      FREE <line>.

    LOOP AT ttab ASSIGNING <line>.
      FREE <line>.

    LOOP AT otab ASSIGNING <line>.
      FREE <line>.

    BREAK-POINT ##no_break.


At the breakpoints, you can use the ABAP Debugger to display the memory requirements of the four internal tables itab, rtab, ttab, and otab.

At the first breakpoint, the four tables have the same dynamic yet not duplicative data content, that is, 1000 different integers. Whereas for itab, the data content size of about 4 MB is only increased by the management costs for itab itself amounting to around 100 bytes, all other tables create management costs for each single table row. For the deep row types in rtab, ttab, and otab, the data content size of 4 MB is confronted with management costs in the order of 100, 200 and 300 MB. The costs for the inner internal table in ttab are higher than that for the data reference in rtab. The management costs for otab are made up of the costs for the object references and for the internal tables in the object references.

At the second breakpoint, all rows of each of the four tables were initialized using FREE. Of course, this does not effect the memory requirements of itab. In rtab, all data as well as all management information of the individual reference variables was deleted, leaving memory requirements of about 8 MB for the initial references plus the management costs for rtab itself. In ttab, all data was deleted but the individual table headers were retained. Although the management costs could be reduced slightly this way, this still leaves about 100 MB of pure management costs. For otab, by contrast, the situation was similar to rtab, leaving only the costs for the initial references.

This example shows on the one hand that for internal tables with deep row types the management costs may easily exceed the data content and on the other hand that after deleting data a table with object references is less expensive than a table with inner tables.