CDS – 23: CDS Performance Analysis – Basics – 1

eLearning Solutions - Blog - CDS – 23: CDS Performance Analysis – Basics – 1
CDS – 23: CDS Performance Analysis – Basics – 1
  • 06 Sep
  • 2024

Compact discs Perspectives work on the code pushdown system where the information concentrated computations/collections are finished in the DB layer (rather than the conventional application layer), which gives a lift to execution. Let’s go in CDS – 23: CDS Performance Analysis – Basics – 1.

Everyones assumption is that with the code pushdown the wizardry ought to happen like clockwork. The presentation ought to continuously be better on the off chance that not advanced. Be that as it may, companions in genuine task situations, everything is certainly not a cheerful way. There have been cases where the inquiry doesn’t give the normal presentation elevate. In this multi-part series, we will initially take a gander at dissecting the exhibition of the basic question and afterward articulate various ways of tuning it.

The web is overflowed with Center Information Administrations, however you will scarcely find any great instructional exercises or series on Advancement and Execution Tuning of ABAP Center Information Administrations. Ideally, this series will help our SAP Brotherhood. CDS – 23: CDS Performance Analysis – Basics – 1.

Basics First.

  • ABAP Cds sees are created utilizing ADT and their execution occurs in the DB.
  • Scientific Question Cds act uniquely in contrast to Utilization View Albums due to the hidden comments which influence execution (We will examine this To some degree 2).
  • It is feasible to investigate Logical Inquiry Discs through exchange RSRT to recognize Fiori or approval related issues. This is one of the initial steps prescribed to segregate and recognize assuming that the issue is execution related.
  • To comprehend the execution, we really want to distinguish the SQL articulation that is created by the Compact discs. (Here we should give close consideration to the genuine factors and worth that are utilized).

For instance: Execution of Preliminary Equilibrium Albums (IFIGLBALCUBE/I_GLACCTBALANCECUBE) in 1709 produces the accompanying SQL explanation.

You can definitely relax, we will find in the ensuing presents on how on get this SQL explanation.

SELECT /* CDS access control applied */ "COMPANYCODE" "K____360" , 
"CHARTOFACCOUNTS" "K____359" , 
"GLACCOUNT" "K____366" , 
"FISCALPERIODDATE" "K____443" , 
"COMPANYCODECURRENCY" "K____479" , 
COUNT(*) "Z____110_SUM" , SUM( "DEBITAMOUNTINCOCODECRCY" ) 
"Z____3159_SUM" , SUM( "ENDINGBALANCEAMTINCOCODECRCY" ) 
"Z____3163_SUM" , SUM( "CREDITAMOUNTINCOCODECRCY" ) 
"Z____3187_SUM" 
FROM /* Entity name: I_GLACCTBALANCECUBE CDS access controlled */ 
"IFIGLBALCUBE" ( "P_FROMPOSTINGDATE" => ? , "P_TOPOSTINGDATE" => ? ) 
"A1" WHERE "MANDT" = ? AND "COMPANYCODE" = ? AND 
"LEDGER" = ? GROUP BY "COMPANYCODE" , "CHARTOFACCOUNTS" , 
"GLACCOUNT" , "FISCALPERIODDATE" , 
"COMPANYCODECURRENCY" ORDER BY "A1" . "COMPANYCODE" , "A1" . 
"GLACCOUNT"  WITH HINT
(DOUBLE_PREAGGR_BEFORE_JOIN,USE_OLAP_PLAN,RESULT_LAG ('hana_long')) 
WITH RANGE_RESTRICTION('CURRENT')
  • In the event that the Compact discs view has approval limitations through DCL (Information Control Language) this will have an essential impact in the SQL explanation framed. In the past proclamation, “Cds access control” shows that a relating DCL exists and approval limitations have been applied during execution.
  • In the event that Compact discs question has DB hints (prev model has HINT(DOUBLE_PREAGGR_BEFORE_JOIN,USE_OLAP_PLAN,RESULT_LAG (‘hana_long’))) as a feature of the explanations, this will likewise have an impact in the execution plan(creation of the SQL proclamation) of the Cds.
  • Cds sees work on a stacking model. (Sees are stacked and reused to accomplish more prominent adaptability and strength). On the off chance that the stacking is poor, this will be a channel on the presentation.

How to understand the stacking model?

In ADT, subsequent to opening the connected Discs view, right snap and pick

Open With -> Dependency Analyzer.

  • This will open the SQL Reliance Tree which shows how the choice occurs starting from the top

Really focus on the Tabs at the lower part of the screen.

  • SQL Dependency Graph is a visual portrayal of the Tree and assists you with better grasping the information base choice. (This is a decent device to use to eliminate any undesirable branches from the SQL question to upgrade the presentation).
  • Complexity Metrics give an obvious sign of the quantity of data set tables utilized by the Discs view. (kindly note that runtime affiliations are excluded from this rundown just plan time affiliations, joins, associations, collections and so on.)

This gives a fundamental thought on how Discs view work in the engine and what are the significant contemplations that influence execution. In the accompanying posts, we will take a gander at the SQL explanation, Plan Viz, Execution Plan and Comments to tweak and accomplish ideal execution.

This is only a hint of something larger. We will jump all the more profound to get better understanding of the Cds Execution Tuning. Kindly stay tuned.

 

YOU MAY LIKE THIS

What salary should you expect in SAP industry?

Transaction to launch Fiori launchpad

What is replication flow in Datasphere?

WhatsApp WhatsApp us