-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
The worker container consistently uses around 25% of CPU resources even when I'm not performing any actions in DIFY. #12281
Comments
The worker container in Dify handles various asynchronous tasks, such as document indexing and dataset updates, using Celery. These tasks are typically triggered by specific actions, but there is no explicit mention of tasks running continuously or periodically when the system is idle [1]. To investigate the high CPU usage, you can check the logging mechanisms in place. Dify includes logging configurations that can help identify what the worker container is doing at any given time. You can adjust the logging settings in the Additionally, you might want to review the environment variables related to Celery workers, such as To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
My Another weird thing is that after I get into the worker container's shell, I'm unexpectedly kicked back to the host pretty quickly, even without doing anything. It feels pretty strange. |
A continuous restart loop for the worker container in Dify can be caused by several factors:
Since the logs only show To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
it seems nothing wrong in the logs. |
and although worker is always restarting, DIFY system seems normal |
now DIFY can't start up after I do a restart. |
This error suggests you missed a migration version 'd7999dfa4aae'. Please check you have follow the upgrade instructions. If not, please remove the containers and images to start it again. |
I've got a hunch about the cause. Last week I upgraded from 0.14.1 to 0.14.2, but then I rolled back to 0.14.1 due to a file bug. That's when the high CPU usage began. The system remained usable, but if I restarted DIFY it would fail to start. Upgrading back to 0.14.2 then fixed it. Downgrading to 0.14.1 would let me access the system again, but it wouldn't survive a restart. So I'm counting on your new version release now. |
I have a similar problem, my N100 host is almost unusable due to lag |
Self Checks
Dify version
0.14.1
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
do nothing
✔️ Expected Behavior
When DIFY is not being used, it should have CPU usage similar to other DIFY containers, either occupying CPU0 or having very low usage.
❌ Actual Behavior
The text was updated successfully, but these errors were encountered: