Excessive disk activity? #909
-
Hi all, not sure if this is a bug or something which can be resolved by tweaking the configuration of NJSPC. However I am experiencing non-stop disk activity when NJSPC is running. I've been running it for a long time on a Pi, but since the SD card crashed last year I moved NJSPC to run as a docker container on my Synology 920+ NAS, using their Container Manager + an EW-11 network RS485 server. Everything works nicely. However I've noticed my disks in my NAS are churning non-stop when I have the poolcontroller container running. I've verified that I have no logging options enabled as well as I have zero of the advanced features (heaters, chems, lights, rem, etc.) enabled. I basically just use NJSPC for controlling the speed of my IntelliFlo-VS pump and reading the watts, that's really all. I can post copies of my config.json files, but there's not that much interesting in them. My docker file looks like this:
My thought is that if no logging is enabled, why would it need to have this much if any disk activity, once loaded up, it should just be all comms and ram, right? Any suggestions are welcome! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
I'm not a Docker expert, but here are some things to look for:
|
Beta Was this translation helpful? Give feedback.
-
So, I learned a ton today:
Already here it was pretty obvious what was going on 1) the mappings of interior folders/files to external access was somehow borked and effing verbose logging was on as well.
Anyway, I'm back on track, the poolcontroller is no longer generating disk activity, rainbows and unicorns all around! :) |
Beta Was this translation helpful? Give feedback.
So, I learned a ton today:
Already here it was pretty obvious what was going on 1) the mappings of interior folders/files to external access was somehow borked and effing verbose logging was on as well.
You can open a terminal side by side with the console into the container: Hit the Create button, then use /bin/sh or /bin/bash (whatever works) and whoopee we were in.
To my dismay I found out I could not edit any files with vi inside the container session. What I had overlooked was that the t…