We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
引擎层scheduler_queue创建了指定数量的线程,应用层动态创建graph过程中,线程缺少管理方案,未来有考虑线程池方案吗。或者能将exec_loop发送给外部线程池管理吗
The text was updated successfully, but these errors were encountered:
目前这方面的需求不太强,原因有几个:
给外部线程池管理,是从哪些角度的考虑?
Sorry, something went wrong.
目前这方面的需求不太强,原因有几个: 线程数量不多。框架引擎层的线程使用数量是相对固定的,且数量较少,只用于多个scheduler。 线程没有频繁的创建销毁动作。 给外部线程池管理,是从哪些角度的考虑?
单个graph的线程使用数量相对固定,多个(3~5个)graph,同时单个graph动态更新时,线程会频繁创建销毁
动态更新场景是个值得加入线程池的地方。 如果有可参考的这种demo,后续可以基于demo场景专门做一波优化。
No branches or pull requests
引擎层scheduler_queue创建了指定数量的线程,应用层动态创建graph过程中,线程缺少管理方案,未来有考虑线程池方案吗。或者能将exec_loop发送给外部线程池管理吗
The text was updated successfully, but these errors were encountered: