[QUESTION] Memory consumption seems high

[DennisGaida]

Environment

Self-Hosted (Docker)

Version

2.0.1

Describe the problem

Checking my docker stack, dashy is almost the highest consumer of RAM/memory with currently 255MB assigned to it. I'm just wondering whether this is "normal"? Dashy ultimately is a static HTML page being served and I believe that is a bit much RAM for a HTML page...

Am I missing some caching mechanism I haven't activated? I haven't restarted the container no, so maybe I'm experiencing a memory leak?

Additional info

No response

Please tick the boxes

• You are using a supported version of Dashy (check the first two digits of the version number)
• You've checked that this issue hasn't already been raised
• You've checked the docs and troubleshooting guide
• You agree to the code of conduct

[Lissy93]

Heya @DennisGaida,
I think it's the Node server consuming memory, but it should only happen when the container rebuilds. Node.js is notoriously heavy, but there is a lite version planned (see roadmap).

In the meantime, you can serve up the static files yourself with NGINX or similar web server (here's an example: Dockerfile). Only downside is that the server-side endpoints (update config, status check, and proxy widget results) will not work, and you currently won't be able to modify config.

Going to close this as a duplicate, but if you've got a mem dump, or more info that shows there's a bug, or if the memory has massively spiked between versions, then this would be a bug, so feel free to reopen.

[DennisGaida]

Thank you for answering this @Lissy93! I'm sure it is node, I just thought that maybe there was something to make it leaner.

Looking forward to the lite version - I'll keep running the current version w/o nginx since 250MB isn't too bad, but I was still wondering where all that memory goes.

[Hakker]

Well lite version should happen soon then because in recent versions it has been growing to roughly 465 MB.