#LoadBundleEntry

LoadBundle refers to the initial frame rendering pipeline triggered by LynxView loading and executing the TemplateBundle. LoadBundleEntry is used to record the performance data of this rendering pipeline and inherits from PipelineEntry.

The LoadBundle process flowchart is as follows:

#Example

This example demonstrates how to obtain a LoadBundleEntry.

performance-apisrc/load-bundle-entry/index.tsx

Preview

#Instance properties

#entryType

entryType: string;

The type of the performance event; the value for all instances of this class is fixed as pipeline.

#name

name: string;

The specific name of the performance event; the value for all instances of this class is fixed as loadBundle.

#identifier

identifier: string;

A marker for a particular rendering pipeline; the value for all instances of this class is fixed as an empty string.

#loadBundleStart

loadBundleStart: number;

The timestamp for the start of loading and executing the TemplateBundle. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#loadBundleEnd

loadBundleEnd: number;

The timestamp for the end of loading and executing the TemplateBundle. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#parseStart

parseStart: number;

The timestamp for the start of parsing the TemplateBundle. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#parseEnd

parseEnd: number;

The timestamp for the end of parsing the TemplateBundle. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#loadBackgroundStart

loadBackgroundStart: number;

The timestamp for the start of loading and executing the background thread scripts in the TemplateBundle. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#loadBackgroundEnd

loadBackgroundEnd: number;

The timestamp for the end of loading and executing the background thread scripts in the TemplateBundle. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#pipelineStart

pipelineStart: number;

The timestamp for the start of the rendering pipeline. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#pipelineEnd

pipelineEnd: number;

The timestamp for the end of the rendering pipeline. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#mtsRenderStart

mtsRenderStart: number;

The timestamp for the start of executing the main thread scripts to build the Element Tree. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#mtsRenderEnd

mtsRenderEnd: number;

The timestamp for the end of executing the main thread scripts to build the Element Tree. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#resolveStart

resolveStart: number;

The timestamp for the start of calculating Element styles. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#resolveEnd

resolveEnd: number;

The timestamp for the end of calculating Element styles. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#layoutStart

layoutStart: number;

The timestamp for the start of layout calculations. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#layoutEnd

layoutEnd: number;

The timestamp for the end of layout calculations. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#paintingUiOperationExecuteStart

paintingUiOperationExecuteStart: number;

The timestamp for the start of executing UI operations related to painting. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#paintingUiOperationExecuteEnd

paintingUiOperationExecuteEnd: number;

The timestamp for the end of executing UI operations related to painting. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#layoutUiOperationExecuteStart

layoutUiOperationExecuteStart: number;

The timestamp for the start of executing UI operations related to layout. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#layoutUiOperationExecuteEnd

layoutUiOperationExecuteEnd: number;

The timestamp for the end of executing UI operations related to layout. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#paintEnd

paintEnd: number;

The timestamp for the end of completing the final pixelation based on UI and UITree. This timestamp is represented as a floating-point Unix timestamp (in milliseconds) with three decimal places. For example: 1739594612307.429.

#frameworkPipelineTiming

frameworkPipelineTiming: FrameworkPipelineTiming[keyof FrameworkPipelineTiming];

Performance data for key stages in Framework Rendering. The type is FrameworkPipelineTiming.

#hostPlatformTiming

hostPlatformTiming: AndroidHostPlatformTiming |
  HarmonyHostPlatformTiming |
  IOSHostPlatformTiming;

Performance data for platform-specific key stages in Lynx Pipeline, with type AndroidHostPlatformTiming | HarmonyHostPlatformTiming | IOSHostPlatformTiming.

#Compatibility