API calls are not efficient for multiple qps

[sjy234sjy234]

Self Checks

• [x] I have searched for existing issues search for existing issues, including closed ones.
• [x] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• [x] Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

It is very productive that we design a workflow directly as an api. However, I found that the api excution costs much resources and runs quite slow. It seems not suitable for the api directly serves as an efficient production backend, e.g., as efficient as those api specifically written in nodejs. Maybe it needs a compiler and a runner to achieve this runtime efficiency. Is there a plan on this?

2. Additional context or comments

No response

3. Can you help us with this feature?

• [ ] I am interested in contributing to this feature.

[xbpeng121]

I think there is nothing about node.js，the workflow apis are on the port 5001 which is hosted by the api_server written by python on Flask framework

[dosubot[bot]]

Hi, @sjy234sjy234. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

• You raised a concern about the inefficiency of API calls at high query rates.
• Suggested the need for a compiler and runner to improve runtime efficiency.
• @xbpeng121 noted that the issue is unrelated to Node.js and mentioned the APIs are hosted on port 5001 using Flask.
• You mentioned not being interested in contributing to the development of this feature.

Next Steps:

• Could you confirm if this issue is still relevant to the latest version of the Dify repository? If so, please comment to keep the discussion open.
• If there are no further updates, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!