I’m running pihole as a container on my L009UIGS and it works like charm when it’s a fresh install, it is installed on a USB drive.
But after some time (probably around 2 weeks) it is dramatically slowing down. I can notice when it’s happening since the simple internet browsing is becoming a slower due to the fact that the pihole DNS is timing out and then the devices (my laptop…etc) are falling back to the secondary DNS.
Still responding to ping, but If I’m trying to reach the admin page it’s timing out.
Container restart doesn’t help, even when it’s starting I can see in the logs that it’s initial booting of the container is very slow and kind of neverending.
Whole router restart doesn’t help same thing is happening.
The only thing helps is if I remove the container completely and then recreating it and then it’s again immediately working normally.
After this when I login to pihole then in the diagnosepage I can see a former log entry that there was very high CPU usage logged within the pihole:
"Long-term load (15 min avg) larger than number of processors: 3.2 > 2
This may slow down DNS resolution and can cause bottlenecks. "
While the in the same time Router CPU is rarely going above 8%.
Good point. I’ll monitor it now for a while to see if it’s increasing. About 1,5m entries are in the list, and it’s not using much RAM at the moment, but it’s not a fresh install again. Let’s see where it goes I’ll report back in a few days.
Running for 2 days only and it’s in a very very light use only 1 laptop is using it now. No problem with the RAM, but look at the CPU load. It’s already unreachable and timing out.
your “top” output doesn’t show high CPU usage (at only 5% of a single core), but it does show high load. Time a process spends in processing or waiting to do so contribute to the load, but so do things in iowait. This latter is what is the problem.
