The attribute setting process of FrameNode is longer than that of ArkTS. This is because ArkTS uses the declarative UI paradigm and generates complete attribute configurations during compilation. FrameNode, as an imperative UI node, needs to dynamically apply attribute changes during running. ArkTS sets all attributes of a component at a time, while FrameNode sets each attribute of a node one by one. Each attribute setting requires a cross-language communication, increasing the performance overhead. If you need to dynamically modify the component tree or reuse components, you are advised to set or modify only necessary attributes to optimize performance.