For AI agents: the complete documentation index is available at /next/llms.txt, the full documentation bundle is available at /next/llms-full.txt, and this page is available as Markdown at /next/api/lynx-api/performance-api/framework-pipeline-timing.md.
Lynx
  • English
  • FrameworkPipelineTiming BTS

    This interface describes the performance data of key stages in framework rendering.

    Instance Properties

    dsl

    dsl: string;

    A string describing the DSL type, with a default value of reactlynx.

    stage

    stage: string;

    A string describing the type of framework data update process, with possible values hydrate and update. hydrate refers to the process of calibrating and updating main thread data using background thread data, while update refers to updates triggered in useEffect. For more information, see ReactLynx Lifecycle.

    diffVdomStart

    diffVdomStart: number;

    The timestamp when the framework starts VDom Diff on the background thread. This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.

    diffVdomEnd

    diffVdomEnd: number;

    The timestamp when the framework ends VDom Diff on the background thread. This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.

    packChangesStart

    packChangesStart: number;

    The timestamp when the framework starts serializing change information on the background thread. This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.

    packChangesEnd

    packChangesEnd: number;

    The timestamp when the framework ends serializing change information on the background thread. This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.

    parseChangesStart

    parseChangesStart: number;

    The timestamp when the framework starts deserializing change information on the main thread. This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.

    parseChangesEnd

    parseChangesEnd: number;

    The timestamp when the framework ends deserializing change information on the main thread. This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.

    patchChangesStart

    patchChangesStart: number;

    The timestamp when the framework starts applying change information on the main thread. This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.

    patchChangesEnd

    patchChangesEnd: number;

    The timestamp when the framework ends applying change information on the main thread. This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.

    hydrateParseSnapshotStart

    hydrateParseSnapshotStart: number;

    The timestamp when the framework starts deserializing main thread information on the background thread. This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.

    Tip

    This property is only valid when stage is hydrate.

    hydrateParseSnapshotEnd

    hydrateParseSnapshotEnd: number;

    The timestamp when the framework ends deserializing main thread information on the background thread. This timestamp is a floating-point Unix timestamp (in milliseconds), accurate to three decimal places. For example: 1739594612307.429.

    Tip

    This property is only valid when stage is hydrate.

    Compatibility

    LCD tables only load in the browser

    Except as otherwise noted, this work is licensed under a Creative Commons Attribution 4.0 International License, and code samples are licensed under the Apache License 2.0.