topic Re: Memory in Application Development and Automation Discussions

Memory

Former Member — Thu, 22 Jan 2009 17:35:36 GMT

Hi gui's.

After excuting the programe how to find on which internal table how many entries are there.

And how much memory that programe is taking.

Thanks and regards

santhosh

Edited by: Julius Bussche on Jan 22, 2009 7:50 PM

Please use meaningfull subject titles and search before asking questions which others must have asked before you already...

Re: Memory

rodrigo_paisante3 — Thu, 22 Jan 2009 18:01:06 GMT

Hi,

you can use SE30 to check performance in your program.

Just put you program or transaction, EXECUTE it and came back and click in EVALUATE. It will show you how much time is taking.

Regards.

Re: Memory

MarcinPciak — Thu, 22 Jan 2009 18:53:07 GMT

Hi,

As Rodrigo said, use [ABAP runtime trace - se30|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/7769] [original link is broken] [original link is broken] [original link is broken];

Regards

Marcin

Re: Memory

Former Member — Fri, 23 Jan 2009 06:34:36 GMT

search in se 30 ,st05

Re: Memory

Former Member — Thu, 05 Feb 2009 09:39:57 GMT

you can calculate the number of entries of an internal table by DESCRIBE statement.

You can also use transactions SE30 to see the performance of the program.

Re: Memory

Former Member — Tue, 10 Feb 2009 10:58:26 GMT

Hi ,

You can use SE30 or ST05 to know about the performance analysis of a program.

For using ST05 you may use this link :

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5a1de990-0201-0010-8d83-a06bdda1d7d5

Regards,

Radhika.

Re: Memory

Former Member — Tue, 10 Feb 2009 14:27:52 GMT

> to find on which internal table how many entries are there

debugger

> memory

ABAP Trace: measurement restriction last page: no aggregation plus memory

Siegfried

Re: Memory

HermannGahm — Wed, 11 Feb 2009 16:15:42 GMT

Hi,

well after execution... only STAD could give a overall memory consumption for your program but no details for internal tables.

During execution: as already mentioned: Debugger, Memory Inspector (for internal tables) and anaggregated SE30 with memory consumption for overall memory consumption will help you.

Kind regards,

Hermann