Further Testing Results: High CPU Usage with Default Docker Image of Open-WebUI on aaPanel
Hello again,
I wanted to share an update based on additional testing to help further diagnose this issue.
Additional Testing in Local Lab Environment
To isolate the problem, I set up a new environment in my local lab using aaPanel without SSL, and I deployed the default Docker image of open-webui. Here are the results:
Same High CPU Usage:
Despite running in a local lab environment without SSL, the high CPU usage issue persists.
As soon as I upload files (especially larger ones), the CPU usage spikes, much like in my online project. Interestingly, the process seems faster on the local setup, but it still reaches high CPU levels.
Environment Details:
This time, I used a completely fresh aaPanel installation with the default configuration and no SSL or reverse proxy.
The issue remains specific to aaPanel, as the same Docker image (open-webui) doesn’t have these problems in other environments (Ubuntu + Docker without aaPanel).
Summary of Findings
It appears that the high CPU usage issue with open-webui on Docker persists regardless of SSL settings or network environment, suggesting that it might be related to how aaPanel handles Docker container processes or interacts with them.
Next Steps and Request for Guidance
Given that this issue is reproducible in different aaPanel environments, are there any specific Docker or aaPanel configurations that might reduce CPU usage?
If anyone else has encountered similar issues or has insights into optimizing aaPanel’s interaction with Docker containers, I’d greatly appreciate any advice.
Thank you!
