Re: [Dnsmasq-discuss] About resolution performance and adblock

2024-11-25 Thread Ercolino de Spiacico
The amount of resources we have on a router are very limited. That is mainly the reason why we used dnsmasq initially. Wireless drivers keep us jailed to Kernel 2.6 for the time being, and this is also another limitation that could prevent a Pi-hole to be even be considered, as backporting is

Re: [Dnsmasq-discuss] About resolution performance and adblock

2024-11-25 Thread Buck Horn via Dnsmasq-discuss
Hi Ercolino, On 24.11.24 17:26, Ercolino de Spiacico wrote: (...) Also, Pi-Hole requires additional HW, where FreshTomato runs on a simple router with optional USB storage. pihole-FTL may require more resources to run than plain dnsmasq (mostly memory), but it does not tie to any specific hard

Re: [Dnsmasq-discuss] About resolution performance and adblock

2024-11-24 Thread Ercolino de Spiacico
Hi Buck, thank you for the new info you brought up in your message I should have mentioned: I'm not an adblock user reporting performance issue here or lookign for alternatives, but rather the developer of adblock (currently in version 2.78m) for FreshTomato; so switching to Pi-hole somehow de

Re: [Dnsmasq-discuss] About resolution performance and adblock

2024-11-22 Thread Buck Horn via Dnsmasq-discuss
Hi Ercolino, On 19.11.24 17:31, Ercolino de Spiacico wrote: In the context of Adblock, I noticed that our adblock script can handle relatively well about 10MB of blockfile which is about 7.8% of the device RAM (128MB), after that the resolution time increases exponentially to the point where the

Re: [Dnsmasq-discuss] About resolution performance and adblock

2024-11-21 Thread Donald Muller
4 9:54 AM > To: Leonid Evdokimov ; imn...@gmail.com > Cc: dnsmasq-discuss@lists.thekelleys.org.uk > Subject: Re: [Dnsmasq-discuss] About resolution performance and adblock > > Indeed, I think the point is straight forward, there are part of dnsmasq > where we do want to compl

Re: [Dnsmasq-discuss] About resolution performance and adblock

2024-11-20 Thread Ercolino de Spiacico
Indeed, I think the point is straight forward, there are part of dnsmasq where we do want to comply with RFC, etc, others that are locally significant only and can bypass certain check, adblock being one of those. There are a number of lists I can suggest, see this link we maintain: https://wi

Re: [Dnsmasq-discuss] About resolution performance and adblock

2024-11-20 Thread Chris Green
On Wed, Nov 20, 2024 at 04:06:08PM +0300, Leonid Evdokimov wrote: > On Tue, Nov 19, 2024 at 8:05 PM Ercolino de Spiacico > wrote: > > If given the possibility, I would be very happy to map a file in RAM > > knowing that > > this is handled differently from the "standard" conf-file. > > I agree w

Re: [Dnsmasq-discuss] About resolution performance and adblock

2024-11-20 Thread Leonid Evdokimov
On Tue, Nov 19, 2024 at 8:05 PM Ercolino de Spiacico wrote: > If given the possibility, I would be very happy to map a file in RAM knowing > that > this is handled differently from the "standard" conf-file. I agree with this point and I'm developing libddt (dense domain table) that is basically

Re: [Dnsmasq-discuss] About resolution performance and adblock

2024-11-19 Thread imnozi
FWIW, I use (on a 32-bit i686 appliance) a 33MiB ads/pron/warez blocklist of 1.2M domains in the form "local=/FQDN/" (that is, the domains do not exist at all for me; I'm OK with seeing whitespace). The virtual size (from 'ps aux') of the running dnsmasq is 175MiB. Resolution time is a hair slow