applemili.blogg.se - App startup time

In addition, the browser loads all required CSS files in parallel. The SAPUI5 Core gets loaded first and ensures a parallel loading of all required libraries. 29 requests and fully loaded in a little over 6 seconds. New sap.ui.xmlview().placeAt("content") īy wrapping our application code in the callback function passed to the attachInit event, we can ensure that all SAPUI5 libraries are available and thus can avoid the additional sync requests. Understanding the bootstrapping within index.html

manifest.json: This file is the metadata description of the application and also found in most modern SAPUI5 applications.

Component.js: Modern applications (which follow the official SAPUI5 best practices and all modern SAPUI5 Fiori applications) have this file which represents the application component.

view: Typically XML files for all view definitions.

util: Typically a set of Javascript files needed by the application (folder name is not standardized, but most applications have such a folder with additional JS code).

model: Application specific models and their respective modules for implementation.

i18n: Contains the properties files which contain the application’s resource files in their respective translation.

css: Application specific CSS files (if required).

controller: Javascript files with the controller implementations for the corresponding views.

The application consists of all typical folders and their included artifacts. The initial startup time of this application is around 8s – we will optimize it to around 2s. You can get the sources of the sample application here: We will use a very simple application for this exercise, one which nonetheless has all of the key structures and artifacts found in “typical” applications and thus serves quite well to illustrate the mechanics. In addition, we will look at which effect a high latency can have on your performance and how to best tackle this issue as well using the AKAMAI network.

Optimizing the choreography is key to getting the best possible startup performance. The goal of this post is to outline some of the basic principles which need to be understood in terms how SAPUI5 loads its own resources and those of applications. The initial steps taken to improve the situation actually worsened it and the reasons for this behavior were not understood. I decided a while ago to write this blog post after a call I had with a customer who struggled with the startup performance of his SAPUI5 application.