ERPClimb logoERPClimb
Login
Performance, asynchronous loading and request budgets
Fiori & SAPUI5advanced

Performance, asynchronous loading and request budgets

Full lesson currently free to read · AI practice limits apply separately

Key takeaway

Measure network and rendering separately before optimizing. Asynchronous module loading and suitable preloads reduce avoidable resource waits; selective data requests reduce payload work. A faster loading shell can still hide a slow or over-fetching business query.

Visual overview

Performance, asynchronous loading and request budgetsCompare the expected evidence at the four boundaries. Baseline: Baseline fixture has 60 resource requests and 5000 orders.; Load: Resources arrive through the intended preload path.; Select: The first view consumes ten orders and required properties.; Compare: Measured improvement does not remove required order data.ERPClimb.com · ADVANCED · ORIGINAL TEACHING DIAGRAMPerformance, asynchronous loading and request budgets1. BaselineBaseline fixture has 60 resourcerequests and 5000 orders.2. LoadResources arrive through the intendedpreload path.3. SelectThe first view consumes ten orders andrequired properties.4. CompareMeasured improvement does not removerequired order data.Compare the expected evidence at the four boundariesSynthetic evidence. Verify SAP product, edition, runtime and enabled capabilities.

Explanation

Tutorial outcome

Measure network and rendering separately before optimizing. Asynchronous module loading and suitable preloads reduce avoidable resource waits; selective data requests reduce payload work. A faster loading shell can still hide a slow or over-fetching business query.

Prerequisites

Complete chapters 1–13 in this module. Use synthetic fixtures or an authorized sandbox.

Worked case — fictional

A synthetic order app downloads many small resources and all historical orders before displaying ten rows.

Step-by-step investigation

1. Baseline

Record a cold-load resource waterfall, transferred bytes and time to the first usable task.

Expected evidence: Baseline fixture has 60 resource requests and 5000 orders.

2. Load

Use supported asynchronous component/dependency loading and inspect the generated preload artifact.

Expected evidence: Resources arrive through the intended preload path.

3. Select

Request only the fields and bounded result set needed for the first screen where the service supports it.

Expected evidence: The first view consumes ten orders and required properties.

4. Compare

Re-run the same scenario and confirm functional correctness, navigation and missing-resource behavior.

Expected evidence: Measured improvement does not remove required order data.

Try it yourself

Reproduce the synthetic input from the example below in a local fixture or authorized sandbox. Follow each step, record the observed result, and explain any mismatch before continuing. Do not treat the expected evidence as a result observed in your SAP tenant.

Acceptance check

The same business task is correct with a measured reduction in avoidable resources or data volume.

Common failure to avoid

Do not use unbounded prefetching, synchronous module calls or an unmeasured cache change as a performance strategy.

Self-check

Which evidence should precede a loading optimization?

Expected reasoning: A repeatable resource and business-request baseline.

Edition and release scope

Check the linked SAP documentation for your product, runtime, region and enabled service plan. The worked case is a simulation; these steps were not executed in a customer SAP tenant.

SAP references

References checked 2026-10-30. SAP material supports the named concepts; the case, fixture and acceptance checks are original ERPClimb teaching material. No SAP tenant execution or certification is claimed.

[SAP Help — UI5 developer best practices](https://help.sap.com/docs/SAPUI5/b2f662dd9d7a4ec680056733050b4d34/28fcd55b04654977b63dacbee0552712.html?version=1.143) — Asynchronous modules, components, views, fragments and dependencies; source version 1.143

Code example

Illustrative example
{"baselineOrders":5000,"initialPageSize":10,"measure":["requests","bytes","usable-task-time"]}

Loading guided workshop…

Real project scenario

A synthetic order app downloads many small resources and all historical orders before displaying ten rows.

Common mistakes

Do not use unbounded prefetching, synchronous module calls or an unmeasured cache change as a performance strategy.

Best practices

The same business task is correct with a measured reduction in avoidable resources or data volume. Check the linked SAP documentation for your product, runtime, region and enabled service plan. The worked case is a simulation; these steps were not executed in a customer SAP tenant.

Interview angle

Which evidence should precede a loading optimization? A repeatable resource and business-request baseline.

Practice this lesson

Original educational case studies for SAP consultants, not official SAP certification exam questions. Verify product edition and implementation details against the current SAP documentation.

Quick check

0 of 3 questions attempted

1. Which setting improves UI5 startup performance?

2. What is a request budget for a Fiori app?

3. A list report fires dozens of requests on load. What is a common cause?

Interview questions

1. How do you optimise Fiori app performance?

Answer it in your own words first, then compare.

2. How would you enforce performance budgets in a team?

Answer it in your own words first, then compare.

Check before use: lesson examples are educational, not a guarantee of correctness for your SAP edition or release. Sample code has not been executed on your SAP system. Confirm API availability, syntax, authorizations and business impact in an approved development or test environment.

Related SAP topics