Re: [squid-users] clarification of delay_initial_bucket_level

From: E.S. Rosenberg <esr_at_g.jct.ac.il>
Date: Thu, 27 Sep 2012 21:08:12 +0200

2012/9/27 tcr_at_raynersw.com <tcr_at_raynersw.com>:
>> Hmm, I just noticed Eliazers' reply about how reloading often is a bad
>> idea and one should use ext_acls instead,
>
> I'd be interested to hear why reloading is a bad idea. Squid supports HUP reloading, I've been doing it for years and on my systems it takes about 100ms to do a reload, so even if it blocks for that amount of time it's not a big deal. Unless the reload leaks memory or something, I don't think it's a problem. I have an action item to move my servers to external ACLs, but it's been one of those "if it ain't broke" type things, so I haven't done it yet.
>

I don't think Eliezer meant reloading per se as much as my question
which was reloading every 5 minutes.
I also reload all the time when I write new configs and sometimes I
even end up reloading several times in one minute without my users
feeling it as far as I can tell (or at least they don't feel it enough
to start sending mail saying the Internet is broken).

Either way since I am still building the solution and I definitely
don't want to set my delay_pools to be resetting every 5 minutes I
will probably try to do most of it through external acls and only do
reloading on something like a weekly basis....

Regards,
Eli
Received on Thu Sep 27 2012 - 19:08:18 MDT

This archive was generated by hypermail 2.2.0 : Fri Sep 28 2012 - 12:00:05 MDT