topic Re: Performance Comparison between Inline Code and Forms in Application Development and Automation Discussions

Performance Comparison between Inline Code and Forms

Former Member — Fri, 13 Mar 2009 17:26:46 GMT

A colleague has suggested that modularising code into Forms, rather than using inline code will cause a performance hit because of the required PERFORM statements.

Assuming this is not being done in a ridiculously tight loop is there any significant performance hit with modularisation?

On the same subject are there any reference books which explain in microscopic detail the "runtime" system of SAP, e.g. explaining (probably implicitly) the difference in performance between the two techniques.

(I come from a traditional technical background so I know all about stack based languages, interpreters versus compilers, demand paging, page tables etc.)

Re: Performance Comparison between Inline Code and Forms

Former Member — Fri, 13 Mar 2009 19:21:19 GMT

Welcome to SCN!

Does this help:

[Modularization of Procedural ABAP Code|;

Rob

Re: Performance Comparison between Inline Code and Forms

Former Member — Sat, 14 Mar 2009 15:54:41 GMT

You should modularisation as always in programming, but in ABAP you should not write

too small units, there is no compiler which creates incline code.

Overhead of all modularization units is rather small.

FORMs are useful fpr small reports, but outdated ABAP OO is the way to code right now.

Siegfried

Re: Performance Comparison between Inline Code and Forms

former_member182114 — Mon, 16 Mar 2009 21:12:34 GMT

Hi Jerry,

Please check the report RSHOWTIM (SE38), execute and navigate for each option of ABAP Objects Performance Example.

Each option consist of comparations, sometimes the performance difference is irrelevant, in others cases must represents a huge performance lack.

Since you are new in ABAP context, please evaluate this options.

About FORM x INLINE: It's a good practice to separate your code into form's (or function module) to create a clean code, easy for maintenance, documentation and reusability. It not represent benefits for performance.

Regards,

Fernando Da Ró