Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

线程池相关 #139

Open
x850044053wwt opened this issue Nov 4, 2024 · 3 comments
Open

线程池相关 #139

x850044053wwt opened this issue Nov 4, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@x850044053wwt
Copy link

x850044053wwt commented Nov 4, 2024

引擎层scheduler_queue创建了指定数量的线程,应用层动态创建graph过程中,线程缺少管理方案,未来有考虑线程池方案吗。或者能将exec_loop发送给外部线程池管理吗

@sfeiwong
Copy link
Collaborator

sfeiwong commented Nov 4, 2024

目前这方面的需求不太强,原因有几个:

  1. 线程数量不多。框架引擎层的线程使用数量是相对固定的,且数量较少,只用于多个scheduler。
  2. 线程没有频繁的创建销毁动作。

给外部线程池管理,是从哪些角度的考虑?

@x850044053wwt
Copy link
Author

目前这方面的需求不太强,原因有几个:

  1. 线程数量不多。框架引擎层的线程使用数量是相对固定的,且数量较少,只用于多个scheduler。
  2. 线程没有频繁的创建销毁动作。

给外部线程池管理,是从哪些角度的考虑?

单个graph的线程使用数量相对固定,多个(3~5个)graph,同时单个graph动态更新时,线程会频繁创建销毁

@sfeiwong
Copy link
Collaborator

sfeiwong commented Nov 4, 2024

单个graph的线程使用数量相对固定,多个(3~5个)graph,同时单个graph动态更新时,线程会频繁创建销毁

动态更新场景是个值得加入线程池的地方。 如果有可参考的这种demo,后续可以基于demo场景专门做一波优化。

@sfeiwong sfeiwong added the enhancement New feature or request label Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants