On 29/09/2016 10:44 p.m., Darren wrote: > Hi All > > I have been tinkering with Squidguard for a while, using it to manage > ACL lists and time limits etc. > > While it works OK, it's not in active development and has it's > issues. > > What are the limitations with just pumping ACL lists directly into > Squid and letting it do all the work internally without running a > team of squidguards? CPU mostly. The helpers will use Nx the RAM for N helpers, so Squid technically uses less that way. But since Squid workers are internally single-threaded the CPU time takes from the processing of things through the lists does slow down the workers handling other transactions. There is also the time on startup for loading the data into memory. With big data lists both of those differences can be noticable. There are some RAM differences purely due to the storage formats. We have not particularly optimized Squid ACLs recently for large data sets. > > how efficient is squid now at parsing the text files directly, will i > Need more ram as the list grows? Is it slower or are their > optimizations that I can do? > You will. Regardless of whether you use a helper or Squid. Optimizations center around reducing the list sizes, removing duplication, overlaps and dead entries. For regex ACLs compacting the patterns down helps a lot. Squid will do that itself now but is not very smart about it, so manual optimizations still can have big impact. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
