天天看点

Why UI correction note always has a big static size

Prerequisite knowledge

A simple tool to calculate the total size of a BSP application

Some more technical details about SAP note

My Analysis

Take this simple note for example:

Why UI correction note always has a big static size

Sara has only changed two lines in JavaScript code ( displayed below ):

Why UI correction note always has a big static size

However, when downloading this note, the size of compressed XML stream has unbelievable size of 3.2MB.

Why UI correction note always has a big static size

Among which the delta change occupies 1.7MB:

Why UI correction note always has a big static size

Why? Please have a look at decompressed XML content here.

Why UI correction note always has a big static size
Why UI correction note always has a big static size

However, apart from this code change made by Sara, there are also lots of unrelated code or comment which are also included into the delta change area:

i18n property data

Why UI correction note always has a big static size

unrelated Javascript code

Why UI correction note always has a big static size

Unrelated XML view source code

Why UI correction note always has a big static size

If you use Jerry’s tool to calculate the total static size of My Appointment application, you can get size: 1.5MB.

Why UI correction note always has a big static size

Please notice that this is only the static size. In the runtime, ABAP note tool needs more memory to unpack and apply the delta change to customer system as explained clearly in ABAP help.

Why UI correction note always has a big static size

It means the correction instruction for UI note DOES NOT contain the delta code change, but actually contains lots of other unused statement, which leads to the unnecessary big size of note.

继续阅读