I have adguard on a rpi0w2 and once it's started it runs fine, however with adguardian it gets hammered and uses 50-80% cpu. It would be great if I could disable some of the things monitored, to keep cpu low. I am betting without the query log, for instance, it would take far less processing power to update, and would let me have a smaller terminal to see everything else. I also don't really need to see the filter list all the time. It doesn't change unless I make a change.
It would also be nice to have a tiny mode, similar to pihole -c with some minimal adguard and system stats:
|¯¯¯(¯)_|¯|_ ___|¯|___ Core: v5.17.1
| ¯_/¯|_| ' \/ _ \ / -_) Web: v5.20.1
|_| |_| |_||_\___/_\___| FTL: v5.23
——————————————————————————————————————————————————————————
Hostname: workhole (Raspberry Pi)
Uptime: 15 days, 08:39:16
Task Load: 0.02 0.34 1.52 (Active: 2 of 30 tasks)
CPU usage: 16% (4x 700 MHz @ 116f)
RAM usage: 81% (Used: 383 MB of 475 MB)
HDD usage: 25% (Used: 5 GB of 21 GB)
Pi-hole: Offline (Blocking: 0 sites)
Blocked: 0% (Total: 0 of 0)
Local Qrys: 0% (4 DNS servers)
Last Block:
Top Block:
Top Domain:
Top Client:
I have adguard on a rpi0w2 and once it's started it runs fine, however with adguardian it gets hammered and uses 50-80% cpu. It would be great if I could disable some of the things monitored, to keep cpu low. I am betting without the query log, for instance, it would take far less processing power to update, and would let me have a smaller terminal to see everything else. I also don't really need to see the filter list all the time. It doesn't change unless I make a change.
It would also be nice to have a tiny mode, similar to pihole -c with some minimal adguard and system stats: