Jump to: navigation, search

Fast Startup (Client)


Revision as of 14:49, 9 January 2017 by LGE (Talk | contribs)

UBIK® caches all the local content (which exist on the device) in the devices' memory for fast access. However, as the number of objects grows, the device might become less responsive because of the large memory consumption. Also, the initial loading will take a considerable long time. Therefore, a lazy loading feature is added to allow some of the content to be loaded on demand.

Setting

On the Android client, a setting is provided to control how content is cached in the memory.

IC Attention.pngThe default value for this setting is lazy loading.

On the WinX client, lazy loading is the only mode. Therefore, there is no such setting.

Eager loading

After users log in, all content is initialized and loaded into memory. This includes the content hierarchy, object display names, property values, etc.

IC Hint square.pngOn WinX, this mode is deprecated and the only mode is lazy loading.

Lazy loading

After users log in, only the essential content is loaded initially into memory. For now, this means everything other than the property values (on Android) / or properties and property values (on WinX), which are then loaded on demand. For example, when

  • The icons of objects are to be displayed;
  • Users need to look at the properties of objects;
  • Documents (Thumbnails) are shown.

Comparison between eager loading and lazy loading

Setting Name Memory Usage Loading Delay (See hint below) Initialization Time after Login
Lazy Loading Less More Less
Eager Loading More Less More
IC Hint square.pngLoading delay refers to the time it takes before the next level of content is available during content browsing.
IC Attention.pngAndroid Only: When the setting is changed from lazy loading to eager loading, UBIK® will start loading all the content into memory in the background.

Technical background

  • MetaClass and MetaProperty are not affected by the memory usage setting since they're practically needed all the time;
  • On Android: Once an object's property values are cached under lazy loading setting, they will remain in the memory until one of the following happens:
    • The memory allocated to UBIK® is running low;
    • Offline preparation is finished with branch(es) downloaded.
  • On WinX: In general, properties and property values are only loaded on demand. However, those that are classification related are loaded initially so that certain classification-based calculations do not lead to all other properties being loaded as well.

See also