next-render-worker-pages background CPU usage

[lpld]

Environment

Docker

Version

0.15.2

Describe the problem

Hi, I'm using Homarr 0.15.2 on Unraid (via docker) and noticed that there is some constant activity, even when no Homarr page is open. Once in several seconds there is CPU usage spike, as if there is some regular scheduled job in the Homarr server. By running htop from inside the container I can see that there are several "next-render-worker-pages" processes that suddenly become active for a short period of time:

I wonder what might be the reason for this? Nothing suspicious in the logs. I'm trying to minimize power consumption by my home server, so this situation caught my attention.

Thanks.

Logs

Exporting hostname... Migrating database... yarn run v1.22.19 $ ts-node ./migrate.ts Done in 2.54s. Starting production server... Listening on port 7575 url: http://98f64b93bcc9:7575 ℹ Local icons repository directory exists and contains 0 icons ℹ Local icons repository directory exists and contains 0 icons ℹ Local icons repository directory exists and contains 0 icons ℹ Local icons repository directory exists and contains 0 icons ℹ Local icons repository directory exists and contains 0 icons ℹ Local icons repository directory exists and contains 0 icons ℹ Local icons repository directory exists and contains 0 icons ℹ Local icons repository directory exists and contains 0 icons ℹ Local icons repository directory exists and contains 0 icons

Context

No response

Please tick the boxes

• [X] I confirm that I attached the proper logs
• [x] I've read the docs
• [X] I've checked for duplicate issues
• [X] I've tried to debug myself

[github-actions[bot]]

Hi 👋. Thank you for submitting your first issue to Homarr. Please ensure that you've provided all nessesary information. You can use the three dots > Edit button to update your post with additional images and information. Depending on the current volume of requests, the team should get in conact with you shortly.

[ajnart]

Not exactly sure what it is. Did you search for it on Google before ? I suspect it might be due to some kind of validation of the data that is ran in the background but I can't really verify it

[lpld]

Hi @ajnart, thanks for your answer. I did but couldn't find anything specific. Besides, I'm not really a Node.js guy. I wonder am I the only one who's seeing it? Do your Homarr installations behave the same?

[ajnart]

Hi @ajnart, thanks for your answer. I did but couldn't find anything specific. Besides, I'm not really a Node.js guy. I wonder am I the only one who's seeing it? Do your Homarr installations behave the same?

All instances should have the same. It's a nextjs related issue, I was reading up on some GitHub issue about it

[lpld]

Got it. Ok, it's not really critical, so I guess we can close this one. Thanks.