The HTTP request node responds slowly #8521
Replies: 1 comment
-
I found a similar unsolved discussion regarding the HTTP request workflow node and its timeout parameters [1]. For optimizing the performance of the HTTP request node, you can adjust the timeout settings. The default configuration includes the following timeout settings: "timeout": {
"max_connect_timeout": dify_config.HTTP_REQUEST_MAX_CONNECT_TIMEOUT,
"max_read_timeout": dify_config.HTTP_REQUEST_MAX_READ_TIMEOUT,
"max_write_timeout": dify_config.HTTP_REQUEST_MAX_WRITE_TIMEOUT,
} These settings can be adjusted to optimize performance based on your specific requirements [2][3]. Additionally, integrating Dify with external Ops tools like LangSmith and Langfuse can help diagnose performance issues by providing comprehensive tracking and deep evaluation capabilities. This can help monitor key data points and provide clear visibility and debugging information [4][5]. If you need further assistance, please let me know! |
Beta Was this translation helpful? Give feedback.
-
Self Checks
Dify version
0.8.1
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
Run the http request node, the running time is 0.780s, whether it is normal, if normal, whether it can be optimized
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
Beta Was this translation helpful? Give feedback.
All reactions