#ReloadBundleEntry

ReloadBundle refers to the reload rendering pipeline triggered by the native interface LynxView.reloadTemplate or the frontend framework interface lynx.reload, which causes the rendering pipeline of the TemplateBundle to be reloaded and executed. ReloadBundleEntry is used to record the performance data for the reload pipeline and inherits from PipelineEntry.

The main flowchart for the native interface LynxView.reloadTemplate and the frontend framework interface lynx.reload is shown below.

#Example

This example demonstrates how to obtain a ReloadBundleEntry.

performance-apisrc/reload-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 names of the performance events; the value for events triggered by the native interface is fixed as reloadBundleFromNative; the value for events triggered by the frontend framework is fixed as reloadBundleFromBts.

#identifier

identifier: string;

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

#reloadBundleStart

reloadBundleStart: number;

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

#reloadBundleEnd

reloadBundleEnd: number;

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

#reloadBackgroundStart

reloadBackgroundStart: number;

The timestamp for the start of reloading 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.

#reloadBackgroundEnd

reloadBackgroundEnd: number;

The timestamp for the end of reloading 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.

#Compatibility

LCD tables only load in the browser