What's new

AdGuardHome AdGuardHome vs Diversion - some basics

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

ERamseth2

Occasional Visitor
Here are some basic comparisons I made between AGH (with abp.oisd and with dbl.oisd+mmotti filters) and Diversion on an Asus RT-AX86U with Asuswrt-Merlin 386.5_2

Methodology:

  • I did a fresh install and update of the router (clean flash / reset to defaults after flash) and installed either Diversion or AGH
  • I recorded the total RAM usage from the Asuswrt web page
  • I used various real websites and firefox debug console (F12) and the network tab there and recorded the value for the field called "load."
  • I did this 3x per site. I did not calculate averages (yet).
  • I also opened all the sites in their own tabs and used the stopwatch on my phone to load them all at once. This is obviously subject to human error, but I did my best, as I am only human.
  • Finally, I used DNS Bench to run some DNS benchmarks.

Note: for these tests the RT-AX86U was downstream from a pfsense box that was forcing all DNS to go through itself. The test laptop was downstream from the RT-AX86U on its own subnet and connected by gigabit ethernet. I don't know if this invalidates anything. For my DNS Bench tests, I set the DNS servers to be used as the upstream pfsense box-both on the router's upstream subnet (ethernet here was on its own vlan-x.x.99.x) and on the home subnet (x.x.11.x). I also had the RT-AX86U as one of the DNS Bench entries (x.x.50.x).

Note2: I realized after the fact that I left the 20 lookups per second throttling on in AGH when recording these values. I believe this is why the reliability isn't 100% in the DNS Bench when I was using AGH.

Note3: while I later went on to experiment with pixelserv-tls in the mix, these tests were with a pretty out of the box setup for AGH aside from changing the DNS filter lists.

Results:

diversion - around 58% ram with oisd / large

espn load speeds
8.32s / 7.52s / 7.85s


cnn load speeds
5.78s / 5.53s / 2.97s


reddit load speeds
11.65s / 9.88s / 6.88s


ign load speeds
3.90s / 4.61s / 3.90s


polygon load speeds
2.05s / 1.18s / 1.39s


wikipedia load speeds
716ms / 402ms / 435ms


youtube load speeds
3.37s / 2.19s / 2.20s


yahoo load speeds
4.15s / 5.54s / 4.56s


yahoo sports load speeds
5.61s / 3.00s / 4.46s


weather.com load speeds
2.13s / 1.64s / 735ms


accuweather.com load speeds
2.50s / 2.71s / 2.34s

all reload 19.92s / 20.13s / 21.09s

Code:
DNS BENCH

Final benchmark results, sorted by nameserver performance:
(average cached name retrieval speed, fastest to slowest)

  192.168. 99.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  - Cached Name   | 0.001 | 0.001 | 0.004 | 0.000 | 100.0 |
  - Uncached Name | 0.042 | 0.113 | 0.523 | 0.109 | 100.0 |
  - DotCom Lookup | 0.040 | 0.058 | 0.177 | 0.026 | 100.0 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  192.168. 50.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  + Cached Name   | 0.001 | 0.001 | 0.001 | 0.000 | 100.0 |
  + Uncached Name | 0.040 | 0.117 | 0.503 | 0.114 | 100.0 |
  + DotCom Lookup | 0.041 | 0.060 | 0.136 | 0.024 | 100.0 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  192.168. 11.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  - Cached Name   | 0.000 | 0.001 | 0.001 | 0.000 | 100.0 |
  - Uncached Name | 0.041 | 0.125 | 0.495 | 0.126 | 100.0 |
  - DotCom Lookup | 0.043 | 0.054 | 0.081 | 0.009 | 100.0 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  UTC: 2022-03-29, from 20:13:52 to 20:14:07, for 00:15.309

agh- around 62% ram with abp.oisd

espn load speeds
7.80s / 6.57s / 6.63s


cnn load speeds
5.61s / 4.36s / 3.78s


reddit load speeds
5.97s / 10.54s / 6.87s


ign load speeds
6.72s / 3.37s / 3.32s


polygon load speeds
1.32s / 1.59s / 1.30s


wikipedia load speeds
613ms / 472ms / 487ms


youtube load speeds
3.35s / 2.42s / 2.57s


yahoo load speeds
6.62s / 4.22s / 6.52s


yahoo sports load speeds
5.54s / 2.79s / 3.17s


weather.com load speeds
1.45s / 1.57s / 1.48s


accuweather.com load speeds
4.31s / 2.58s / 2.69s

all reload 21.11s / 17.35s / 17.58s


Code:
DNS BENCH

Final benchmark results, sorted by nameserver performance:
(average cached name retrieval speed, fastest to slowest)

  192.168. 50.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  + Cached Name   | 0.000 | 0.001 | 0.001 | 0.000 | 100.0 |
  + Uncached Name | 0.000 | 0.105 | 0.535 | 0.107 |  95.8 |
  + DotCom Lookup | 0.041 | 0.055 | 0.082 | 0.009 |  97.8 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  192.168. 99.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  - Cached Name   | 0.001 | 0.001 | 0.001 | 0.000 | 100.0 |
  - Uncached Name | 0.039 | 0.107 | 0.354 | 0.081 | 100.0 |
  - DotCom Lookup | 0.043 | 0.056 | 0.147 | 0.017 | 100.0 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  192.168. 11.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  - Cached Name   | 0.001 | 0.001 | 0.001 | 0.000 | 100.0 |
  - Uncached Name | 0.040 | 0.107 | 0.364 | 0.086 | 100.0 |
  - DotCom Lookup | 0.042 | 0.079 | 0.309 | 0.062 | 100.0 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  UTC: 2022-03-29, from 21:31:26 to 21:31:48, for 00:22.245

agh2- around 61% ram with dbl.oisd + mmotti filters

espn load speeds
8.58s / 8.58s / 8.45s


cnn load speeds
4.82s / 3.15s / 2.56s


reddit load speeds
7.02s / 6.50s / 11.74s


ign load speeds
3.78s / 3.80s / 3.69s


polygon load speeds
1.84s / 1.52s / 1.81s


wikipedia load speeds
565ms / 568ms / 508ms


youtube load speeds
4.02s / 2.93s / 2.87s


yahoo load speeds
5.45s / 4.22s / 3.59s


yahoo sports load speeds
5.98s / 4.51s / 4.86s


weather.com load speeds
2.15s / 1.48s / 1.53s


accuweather.com load speeds
3.85s / 2.50s / 2.78s

all reload 15.86s / 13.01s / 12.30s

Code:
DNS BENCH

Final benchmark results, sorted by nameserver performance:
(average cached name retrieval speed, fastest to slowest)

  192.168. 50.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  + Cached Name   | 0.000 | 0.001 | 0.001 | 0.000 | 100.0 |
  + Uncached Name | 0.000 | 0.105 | 0.535 | 0.107 |  95.8 |
  + DotCom Lookup | 0.041 | 0.055 | 0.082 | 0.009 |  97.8 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  192.168. 99.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  - Cached Name   | 0.001 | 0.001 | 0.001 | 0.000 | 100.0 |
  - Uncached Name | 0.039 | 0.107 | 0.354 | 0.081 | 100.0 |
  - DotCom Lookup | 0.043 | 0.056 | 0.147 | 0.017 | 100.0 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  192.168. 11.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  - Cached Name   | 0.001 | 0.001 | 0.001 | 0.000 | 100.0 |
  - Uncached Name | 0.040 | 0.107 | 0.364 | 0.086 | 100.0 |
  - DotCom Lookup | 0.042 | 0.079 | 0.309 | 0.062 | 100.0 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  UTC: 2022-03-29, from 21:31:26 to 21:31:48, for 00:22.245


Conclusion: I decided to use AGH with the dbl.oisd.nl block list + mmotti filters (as detailed elsewhere on this forum). This was based on the "all reload" metrics and the DNS Bench Avg uncached speeds. I also weighed ease of unblocking sites and flexibility in blocking individual devices in interesting ways in my decision.

CAUTION: If you switch to / start using AGH you should know there might be a memory leak somewhere. See: https://github.com/AdguardTeam/AdGuardHome/issues/4437
 
Last edited:
CAUTION: If you switch to / start using AGH you should know there might be a memory leak somewhere. See: https://github.com/AdguardTeam/AdGuardHome/issues/4437
It should also be noted that this issue tracker is using a Mipsle style arch, Asuswrt-Merlin Routers run ARM generation Arch. While this issue tracker may fix it for mipse, we may still require having one open for ARM. While there may be some concerns particularly with not using options like --no-mem-optimization which turns off AdGuardHomes method to optimize its own memory usage, there is no guarantee that there are no other concerns. This would involve testing. I would like for any user up for the task to test out adding arguement --no-mem-optimization for week. Also, test out tweaking memory optimization inside the .yaml file. The issue may not be only adguardhome, but might be something we need to configure at run time, which I can accommodate as defaults for the installer for those who are adventurous at testing and would like to be apart of it.
 
Last edited:
Here are some basic comparisons I made between AGH (with abp.oisd and with dbl.oisd+mmotti filters) and Diversion on an Asus RT-AX86U with Asuswrt-Merlin 386.5_2

Methodology:

  • I did a fresh install and update of the router (clean flash / reset to defaults after flash) and installed either Diversion or AGH
  • I recorded the total RAM usage from the Asuswrt web page
  • I used various real websites and firefox debug console (F12) and the network tab there and recorded the value for the field called "load."
  • I did this 3x per site. I did not calculate averages (yet).
  • I also opened all the sites in their own tabs and used the stopwatch on my phone to load them all at once. This is obviously subject to human error, but I did my best, as I am only human.
  • Finally, I used DNS Bench to run some DNS benchmarks.

Note: for these tests the RT-AX86U was downstream from a pfsense box that was forcing all DNS to go through itself. The test laptop was downstream from the RT-AX86U on its own subnet and connected by gigabit ethernet. I don't know if this invalidates anything. For my DNS Bench tests, I set the DNS servers to be used as the upstream pfsense box-both on the router's upstream subnet (ethernet here was on its own vlan-x.x.99.x) and on the home subnet (x.x.11.x). I also had the RT-AX86U as one of the DNS Bench entries (x.x.50.x).

Note2: I realized after the fact that I left the 20 lookups per second throttling on in AGH when recording these values. I believe this is why the reliability isn't 100% in the DNS Bench when I was using AGH.

Note3: while I later went on to experiment with pixelserv-tls in the mix, these tests were with a pretty out of the box setup for AGH aside from changing the DNS filter lists.

Results:

diversion - around 58% ram with oisd / large

espn load speeds
8.32s / 7.52s / 7.85s


cnn load speeds
5.78s / 5.53s / 2.97s


reddit load speeds
11.65s / 9.88s / 6.88s


ign load speeds
3.90s / 4.61s / 3.90s


polygon load speeds
2.05s / 1.18s / 1.39s


wikipedia load speeds
716ms / 402ms / 435ms


youtube load speeds
3.37s / 2.19s / 2.20s


yahoo load speeds
4.15s / 5.54s / 4.56s


yahoo sports load speeds
5.61s / 3.00s / 4.46s


weather.com load speeds
2.13s / 1.64s / 735ms


accuweather.com load speeds
2.50s / 2.71s / 2.34s

all reload 19.92s / 20.13s / 21.09s

Code:
DNS BENCH

Final benchmark results, sorted by nameserver performance:
(average cached name retrieval speed, fastest to slowest)

  192.168. 99.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  - Cached Name   | 0.001 | 0.001 | 0.004 | 0.000 | 100.0 |
  - Uncached Name | 0.042 | 0.113 | 0.523 | 0.109 | 100.0 |
  - DotCom Lookup | 0.040 | 0.058 | 0.177 | 0.026 | 100.0 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  192.168. 50.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  + Cached Name   | 0.001 | 0.001 | 0.001 | 0.000 | 100.0 |
  + Uncached Name | 0.040 | 0.117 | 0.503 | 0.114 | 100.0 |
  + DotCom Lookup | 0.041 | 0.060 | 0.136 | 0.024 | 100.0 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  192.168. 11.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  - Cached Name   | 0.000 | 0.001 | 0.001 | 0.000 | 100.0 |
  - Uncached Name | 0.041 | 0.125 | 0.495 | 0.126 | 100.0 |
  - DotCom Lookup | 0.043 | 0.054 | 0.081 | 0.009 | 100.0 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  UTC: 2022-03-29, from 20:13:52 to 20:14:07, for 00:15.309

agh- around 62% ram with abp.oisd

espn load speeds
7.80s / 6.57s / 6.63s


cnn load speeds
5.61s / 4.36s / 3.78s


reddit load speeds
5.97s / 10.54s / 6.87s


ign load speeds
6.72s / 3.37s / 3.32s


polygon load speeds
1.32s / 1.59s / 1.30s


wikipedia load speeds
613ms / 472ms / 487ms


youtube load speeds
3.35s / 2.42s / 2.57s


yahoo load speeds
6.62s / 4.22s / 6.52s


yahoo sports load speeds
5.54s / 2.79s / 3.17s


weather.com load speeds
1.45s / 1.57s / 1.48s


accuweather.com load speeds
4.31s / 2.58s / 2.69s

all reload 21.11s / 17.35s / 17.58s


Code:
DNS BENCH

Final benchmark results, sorted by nameserver performance:
(average cached name retrieval speed, fastest to slowest)

  192.168. 50.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  + Cached Name   | 0.000 | 0.001 | 0.001 | 0.000 | 100.0 |
  + Uncached Name | 0.000 | 0.105 | 0.535 | 0.107 |  95.8 |
  + DotCom Lookup | 0.041 | 0.055 | 0.082 | 0.009 |  97.8 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  192.168. 99.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  - Cached Name   | 0.001 | 0.001 | 0.001 | 0.000 | 100.0 |
  - Uncached Name | 0.039 | 0.107 | 0.354 | 0.081 | 100.0 |
  - DotCom Lookup | 0.043 | 0.056 | 0.147 | 0.017 | 100.0 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  192.168. 11.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  - Cached Name   | 0.001 | 0.001 | 0.001 | 0.000 | 100.0 |
  - Uncached Name | 0.040 | 0.107 | 0.364 | 0.086 | 100.0 |
  - DotCom Lookup | 0.042 | 0.079 | 0.309 | 0.062 | 100.0 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  UTC: 2022-03-29, from 21:31:26 to 21:31:48, for 00:22.245

agh2- around 61% ram with dbl.oisd + mmotti filters

espn load speeds
8.58s / 8.58s / 8.45s


cnn load speeds
4.82s / 3.15s / 2.56s


reddit load speeds
7.02s / 6.50s / 11.74s


ign load speeds
3.78s / 3.80s / 3.69s


polygon load speeds
1.84s / 1.52s / 1.81s


wikipedia load speeds
565ms / 568ms / 508ms


youtube load speeds
4.02s / 2.93s / 2.87s


yahoo load speeds
5.45s / 4.22s / 3.59s


yahoo sports load speeds
5.98s / 4.51s / 4.86s


weather.com load speeds
2.15s / 1.48s / 1.53s


accuweather.com load speeds
3.85s / 2.50s / 2.78s

all reload 15.86s / 13.01s / 12.30s

Code:
DNS BENCH

Final benchmark results, sorted by nameserver performance:
(average cached name retrieval speed, fastest to slowest)

  192.168. 50.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  + Cached Name   | 0.000 | 0.001 | 0.001 | 0.000 | 100.0 |
  + Uncached Name | 0.000 | 0.105 | 0.535 | 0.107 |  95.8 |
  + DotCom Lookup | 0.041 | 0.055 | 0.082 | 0.009 |  97.8 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  192.168. 99.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  - Cached Name   | 0.001 | 0.001 | 0.001 | 0.000 | 100.0 |
  - Uncached Name | 0.039 | 0.107 | 0.354 | 0.081 | 100.0 |
  - DotCom Lookup | 0.043 | 0.056 | 0.147 | 0.017 | 100.0 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  192.168. 11.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  - Cached Name   | 0.001 | 0.001 | 0.001 | 0.000 | 100.0 |
  - Uncached Name | 0.040 | 0.107 | 0.364 | 0.086 | 100.0 |
  - DotCom Lookup | 0.042 | 0.079 | 0.309 | 0.062 | 100.0 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+
                Local Network Nameserver


  UTC: 2022-03-29, from 21:31:26 to 21:31:48, for 00:22.245


Conclusion: I decided to use AGH with the dbl.oisd.nl block list + mmotti filters (as detailed elsewhere on this forum). This was based on the "all reload" metrics and the DNS Bench Avg uncached speeds. I also weighed ease of unblocking sites and flexibility in blocking individual devices in interesting ways in my decision.

CAUTION: If you switch to / start using AGH you should know there might be a memory leak somewhere. See: https://github.com/AdguardTeam/AdGuardHome/issues/4437
@ERamseth2 , please keep us aware of your findings as you continue to discover. I have added a voice to the memory leak issue tracker. If you come with more findings that may help we can add them there.
 
@SomeWhereOverTheRainBow I will start a new thread here when I have a full day worth of AGH mem usage logs. Once I do that you can tell me what I can contribute that might help on github issue tracker. I don't recall my github login.
 
@SomeWhereOverTheRainBow I will start a new thread here when I have a full day worth of AGH mem usage logs. Once I do that you can tell me what I can contribute that might help on github issue tracker. I don't recall my github login.
You are fine. I can relay it if you feel anything is pertinent. I'd be looking for htop screenshots (kinda like before and after screenshots). Anything to show your usage between days where the memory leak starts to show up. Any crazy logs as well. @ERamseth2 Great job on the statistics you provided above. I love it.
 
@ERamseth2
Right now i am currently extensively testing --no-mem-optimization, if your test come back conclusive, along side my test, with it being benefitial, I will proceed the path to incorporate it as a runtime arguement.
 
I won't know for a few days. The way I figure I would test is grab the memory logs once per 24hrs just before service restart.
It looks like I won't have to implement it after all, future versions of AdGuardHome remove the faulty "memory optimization hack" AdGuardHome was using.
Reference here:

Specifically

view the changes made to: internal/home/memory.go
 
Here are some basic comparisons I made between AGH (with abp.oisd and with dbl.oisd+mmotti filters) and Diversion on an Asus RT-AX86U with Asuswrt-Merlin 386.5_2

Methodology:

  • I did a fresh install and update of the router (clean flash / reset to defaults after flash) and installed either Diversion or AGH
  • I recorded the total RAM usage from the Asuswrt web page
  • I used various real websites and firefox debug console (F12) and the network tab there and recorded the value for the field called "load."
  • I did this 3x per site. I did not calculate averages (yet).
  • I also opened all the sites in their own tabs and used the stopwatch on my phone to load them all at once. This is obviously subject to human error, but I did my best, as I am only human.
  • Finally, I used DNS Bench to run some DNS benchmarks.

CAUTION: If you switch to / start using AGH you should know there might be a memory leak somewhere. See: https://github.com/AdguardTeam/AdGuardHome/issues/4437
Using the latest "Edge" version, Here is some current .yaml settings I am test. Seems to be overall benefitial to the router memory allotment.
Code:
  cache_size: 524288
  cache_ttl_min: 1200
  cache_ttl_max: 14400
  cache_optimistic: true
  bogus_nxdomain: []
  aaaa_disabled: false
  enable_dnssec: true
  edns_client_subnet: false
  max_goroutines: 300
  ipset: []
  filtering_enabled: true
  filters_update_interval: 72
  parental_enabled: true
  safesearch_enabled: true
  safebrowsing_enabled: true
  safebrowsing_cache_size: 174763
  safesearch_cache_size: 174763
  parental_cache_size: 174763
  cache_time: 30
1649292342802.png

I have tremendously dropped default cache size's and have not noticed any depreciation in performance yet. However, I have noticed the choke hold on the router memory has drastically dropped. I also set the capped 20 queries per second to 50.
Right now the router is idling at about 81%, plus I am running pixelserv-tls along side.
1649292492701.png

Here is my block section of .yaml file

Code:
filters:
- enabled: true
  url: https://dbl.oisd.nl/
  name: OISD-FULL
  id: 1649286551
- enabled: true
  url: https://block.energized.pro/ultimate/formats/domains.txt
  name: Block.Energized.Pro-Ultimate
  id: 1649286554
whitelist_filters:
- enabled: true
  url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/Allowed.list
  name: Allowed.list
  id: 1649286552
user_rules:
- /^ad([sxv]?[0-9]*|system)[_.-]([^.[:space:]]+\.){1,}|[_.-]ad([sxv]?[0-9]*|system)[_.-]/
- /^(.+[_.-])?adse?rv(er?|ice)?s?[0-9]*[_.-]/
- /^(.+[_.-])?telemetry[_.-]/
- /^adim(age|g)s?[0-9]*[_.-]/
- /^adtrack(er|ing)?[0-9]*[_.-]/
- /^advert(s|is(ing|ements?))?[0-9]*[_.-]/
- /^aff(iliat(es?|ion))?[_.-]/
- /^analytics?[_.-]/
- /^banners?[_.-]/
- /^beacons?[0-9]*[_.-]/
- /^count(ers?)?[0-9]*[_.-]/
- /^mads\./
- /^pixels?[-.]/
- /^stat(s|istics)?[0-9]*[_.-]/
- /^(.+[_.-])?eulerian\.net$/
- /^(.+[_.-])?dnsdelegation\.io$/
- /^(.+[_.-])?amp(project)?\./
- /(^|\.).+xxx$/
- /(^|\.).+sexy$/
- /(^|\.).+webcam$/
- /(^|\.).+sex$/
- /(^|\.).+porn$/
- /(^|\.).+tube$/
- /(^|\.).+cam$/
- /(^|\.).+adult$/
- '@@||anti-ad.net^'
- '@@||iij.ad.jp^'
- '@@||stats.foldingathome.org^'
- '@@||stats.stackexchange.com^'
- '@@||www.ad.nl^'
- '@@||www.iij.ad.jp^'
 
Last edited:
@ERamseth2
Right now i am currently extensively testing --no-mem-optimization, if your test come back conclusive, along side my test, with it being benefitial, I will proceed the path to incorporate it as a runtime arguement.
Where do I plug in this argument? In the service file somewhere or in the yaml? or the addon script?

Edit: Nevermind, I found it from your other post. For anyone else wondering, it goes in the /opt/etc/init.d/S99AdGuardHome
 
Last edited:

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top