Script for making Adguard Home write cache to RAM instead of disk

[Vansinnet]

Hi! Would it be possible to create a Dietpi option for AdGuard Home to write its cache to RAM instead of disk? This would save a bit of strain on the memory card and speed up DNS-requests a bit. Of course, this is a temporary solution... but making it permanent would require fstab etc.

I'm not entirely sure here... but wouldn't it be possible to do something like this:

1 - Stop AdGuard Home

dietpi-services stop adguardhome

2 - Create backup of AdGuardHome config

3 - Mount data dir on tmpfs
Create a tmpfs mount at that path (e.g. 256 MB size, adjust if needed):

sudo mount -t tmpfs -o size=256M tmpfs /mnt/dietpi_userdata/AdGuardHome

4 - Restore config into RAM
Copy just the config back, so AdGuard Home can start:

cp -r /mnt/dietpi_userdata/AdGuardHome_backup/* /mnt/dietpi_userdata/AdGuardHome/

5 - Start AdGuard Home

dietpi-services start adguardhome

[MichaIng]

We have a script which does a similar for some Servarr applications, though I am actually not sure whether it still works well with latest versions: https://github.com/MichaIng/DietPi/blob/dev/dietpi/misc/dietpi-arr_to_RAM

Could be tried to be made more flexible/generic. But let's see which "cache" you actually mean, which could slow down DNS queries?

/mnt/dietpi_userdata/AdGuardHome does not exist with our implementation, but /mnt/dietpi_userdata/adguardhome as directory with executable and config. It does not make sense to move those to RAM. /mnt/dietpi_userdata/adguardhome/data holds session and stats databases. The first is only relevant for accessing the web interface, unrelated to DNS queries. The second is not written on query, but synced periodically and asynchronously. The DNS cache is hold in RAM already but the application, not stored to disk persistently. So I do not see any file which could speed up thing by moving it to a tmpfs. Could you elaborate which cache/file/database you mean in particular?