Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

How to get memory consumption for program?

Former Member
0 Kudos
12,479

Hello.

Which field in ST03 are responsible for allocated memory for a program?

I want to get memory consumption - which value in ST03 contain amount of data selected from DB?

1 ACCEPTED SOLUTION
Read only

Former Member
0 Kudos
4,081

Thanks everyone. I think I found solution.

To get statistics by memory concumption in ST03 you can use "Memory Use Statistics" in "Analysis Views".

And you can get it with standard FM SAPWL_WORKLOAD_GET_STATISTIC in return table MEMORY_STATISTIC

9 REPLIES 9
Read only

Former Member
0 Kudos
4,081

Hi Anatoily,

I think in ST05 transaction you will be able to see the details of the records fetched.

Regards,

Santanu Mohapatra.

Read only

0 Kudos
4,081

Hello.

Not exactly.

I need to get total memory consumption (K/M/G bytes) in ST03 statistics. How many memory program consumed during day/week/month

Read only

0 Kudos
4,081

Hope this link will helps you to findout your requirement.

http://www.erpgreat.com/bc041.htm

Regards,

Bastin.G

Read only

former_member217544
Active Contributor
0 Kudos
4,081

once you enter search criteria and press enter, it will take you to a screen which has all the details like below:

In this there is a field memory Used. Is this what you are looking for?

Regards,

Swarna

Read only

0 Kudos
4,081

Hello.

I need to get total memory consumption during day/week/month. As far as I know it must be in ST03.

Read only

bastinvinoth
Contributor
0 Kudos
4,081

Hi Anatoliy STYAPSHIN ,

  • Through SE30, You can see memory consumption of all internal tables of your program.
  • To know what "too much" is, consult a basis. Memory allocation is specified by them.
  • When your program is running, go to SM50 or SM66 and choose the process that is running your piece of code. In the detail screen you'll see general memory consumption of your process along with accesses to the database. check the below link for your reference.
  • http://scn.sap.com/community/abap/testing-and-troubleshooting/blog/2011/01/18/next-generation-abap-r...

Regards,

Bastin.G



Read only

Clemenss
Active Contributor
0 Kudos
4,081

Hi Anatoliy,

from your detailed question it is not easy to guess the purpose.

One solution is to use class CL_ABAP_MEMORY_UTILITIES method GET_TOTAL_USED_SIZE within the program in question. You could use a LOG-POINT (see transaction SAAB) to have a detailed log of memory usage.

But: I don'see your point.

Regards

Clemens

Read only

Former Member
0 Kudos
4,082

Thanks everyone. I think I found solution.

To get statistics by memory concumption in ST03 you can use "Memory Use Statistics" in "Analysis Views".

And you can get it with standard FM SAPWL_WORKLOAD_GET_STATISTIC in return table MEMORY_STATISTIC

Read only

Former Member
0 Kudos
4,081

Hi Anatoliy

Use the User List (transaction SM04) to monitor memory use online and in real time.

The Memory Consumption column in the display shows the total memory allocated to the user.


Use SM04 to monitor long-running transactions that stay open for repeated use and to monitor

the memory consumption of long-running background jobs.


Use the SAP Workload: Single Statistical Records — Overview (transaction STAD (interface in English only) or STADWD (translated interface) for the Web Dynpro version)

to scan for high memory users among completed transactions.

The selection option Show all records, grouped by business transaction may help you by organizing

the display by transaction. The column Memory used (kB) shows the maximum memory used by a transaction in each dialog step.


Use STAD when you have had memory-related short dumps such as SYSTEM_NO_ROLL or TSV_TNEW_PAGE_ALLOC_FAILED or when you have observed Dialog work processes in PRIV status.

The statistic records in the time immediately preceding these events may show which programs were consuming too much storage.

Regards

Suganya