I’ll try tomorrow to disable persistence: I don’t have access to the IWs now (I need to reconnect them and test).
The machine is our own machine: this is a server with an old AMD E350D CPU, running Debian 10.
I’ll try tomorrow to disable persistence: I don’t have access to the IWs now (I need to reconnect them and test).
The machine is our own machine: this is a server with an old AMD E350D CPU, running Debian 10.
Just to give you some hope that it will work out in the end, I have EmonCMS running with MySQL and Redis with about 100 PHPFINA feeds and it’s using about 1% CPU. I have data coming in from the car, solar, heat pump and weather station and some of that is at 6-second granularity.
Oh, and it’s all running inside Docker so that’ll no doubt be draining a bit too.
Apparently I have 653 processes running on this machine!
I’m sure with the help of this community you will prevail.
Thank you for your encouragement @MyForest ! In our situation, there’s the specific case of our IoTaWatts’ management, which is causing the server load issue specifically when uploading historic data. I’ll continue to investigate…
Hello all, I didn’t find the perfect configuration on the server side, so I used the hardware solution: we upgraded the CPU and RAM and we’re fine now.
Thank you all for your support!