[新需求]: Support Key Threads with same scheduling policy as UI and Render Thread

新需求提供了什么功能？

This provides a new interface for applications to specify Key Thread IDs that should be scheduled with the same policy as UI main thread and RenderThread.

该需求带来的价值、应用场景？

This is so they can run UI elements in Dynamic Components on some JS Worker Threads with balanced CPU usage compared with the UI Thread.

More details here:
https://gitee.com/arkui-finland/public-reports/blob/master/dynamic-component-info.md#scheduling-and-performance-of-dynamic-component-js-worker-threads

感谢提交Issue！关于Issue的交互操作，请访问OpenHarmony社区支持命令清单。如果有问题，请联系 @陈明 @tangtiantian2021 @shire-yao @wanglai.yao @zhounanzhao @Nicolas 。如果需要调整订阅PR、Issue的变更状态，请访问链接。

Thanks for submitting the issue. For more commands, please visit OpenHarmony Command List. If you have any questions, please refer to committer @陈明 @tangtiantian2021 @shire-yao @wanglai.yao @zhounanzhao @Nicolas for help. If you need to change the subscription of a Pull Request or Issue, please visit the link.

OpenHarmony / resourceschedule_resource_schedule_service

内容风险标识

新需求提供了什么功能？

该需求带来的价值、应用场景？

评论 (1)

OpenHarmony / resourceschedule_resource_schedule_service .gitee-modal { width: 500px !important; }

内容风险标识

[新需求]: Support Key Threads with same scheduling policy as UI and Render Thread

新需求提供了什么功能？

该需求带来的价值、应用场景？

评论 (1)

搜索帮助

OpenHarmony / resourceschedule_resource_schedule_service