-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[BUG] Startup on 3.1.0 consumes too much cpu #1585
Comments
Hi Could you share a bit more? Does it ever go down, or just the first build? |
Same thing. Updated today and RAM & CPU overloaded |
Could you provide more details? Does dashy always consume such high amouts, just at start? |
I just make repull to update dashy and right after start i see 4 processes "vue-cli-service build", that consume all avaible memory and CPU, so other containers were not avaible. Even console works with huge lags... Only hard reset helps and right after rebbot need to quick stop dashy |
Please be more specific. Does the usage go down after some time, like 5 min at max? How much RAM exactly? The first build of dashy takes a bit more ressources, but there aren't any more rebuilds neccessary later on. |
I've waited about 30 mins, but as other contaniers doesn't working, i do hard reset. |
Just for testing, could you extend it to 3GB RAM ? And would you mind sending a screenshot of the ressource usage from container start to like 10minutes? This can be done with portainer:
Thanks! |
To @twsouthwick 1GB is a bit less for dashy, could you try with 2GB? While I got it to work with a raspberrypi which only has 1GB of RAM, memory management is different compared to like a VM or a big server running dashy. |
Waited till now, so it's about 90 min, no effect. Hard reset VM. |
I've updated it to 3gb, and even with the resource constraints, my VM becomes unresponsive:
I'll try to gather some more details this weekendn |
Out of curiosity, what is the value of rebuilding the dashboard in the container? Why not just ship a prebuilt component with the container? I think historically dashy needed the config as part of the build, but now it doesn't need it, right? It makes the dashboard a fairly heavyweight system as it is. |
I think currently it needs to rebuild for other things like for example auth needs a rebuild, custom css, added files like icons, defaultView change and some other very specific things. So in general file changes or additions not related to conf.yml still require a rebuild. @Lissy93 Please correct me if I'm wrong. |
Thanks, that'd be awesome! Because I really cannot reproduce this here and I think lissy has also never been able to reproduce this issue. |
I've had the same issue as well. I thought it was my issue, so I rebuilt the container, but it just chewed up the CPU and memory again. Edit: I had my watchtower auto update. I just read about the 3.0+ update. |
I'll look into this, as somethings definatley not right here, while Node (used for build) is a bit heavy, it shouldn't ever be consuming that amount of resources. So far, haven't been able to reproduce. @DerLokich - it looks like build is being run multiple times, which is weird because it is only needed once. |
Looks like memory consumption isn't the issue - but it spikes to 20cpus and then the system sends a kill as it's taken all the cpus of the machine. And the system sends a kill:
|
I see logs and it looks like Dashy is building in docker while startup. It looks strange. It consumes almost all my VPS resources (I have a small VPS with 2 CPU and 2GB RAM. It also takes a lot of time, I've been waiting about 5 minutes and Dashy still doesn't start :( There is a part of my docker-compose with Dashy:
|
Environment
Self-Hosted (Docker)
System
Docker version 26.1.1, build 4cf5afa
Version
3.1.0
Describe the problem
After launching the container with switching to 3.1.0, the memory/cpu consumption starts going through the roof. I hadn't put constraints on this container (now I do :)) and it was taking over my VM:
it will cycle through very quickly to take all the available memory/cpu.
Additional info
No response
Please tick the boxes
The text was updated successfully, but these errors were encountered: