[squid-users] Regex optimization

[Yuri Voinov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
 
I propose to nominate for the second place of the contest "The most
inefficient use of computing resources - 2016." :-!:-D

Because first place already occuped. :-D 30 millions pornsites in one
squid's ACL and 7 minutes for squid -k refresh. 8-)


17.06.2016 1:20, Antony Stone пишет:
> On Thursday 16 June 2016 at 21:11:50, Alfredo Rezinovsky wrote:
>
>> Well.. I tried.
>> I need to ban 8613 URLs. Because a law.
>
> Have you considered https://www.urlfilterdb.com/products/ufdbguard.html ?
>
>> If I put one per line in a file and set the filename for an url_regex acl
>> it works. But when the traffic goes up the cpu load goes 100% (even using
>> workers) and the proxy turns unusable.
>
> Er, I'm not surprised.
>
>> I tested and saw my squid can't parse regexes with more than 8192
>> characters.
>> I managed to combine the 8000 uris in 34 regexes using a ruby gem,
and the
>> cpu load stays almost at the same level it is without any acl (same
>> traffic).
>
> That must be *way* past anything to be described as "maintainable".
>
>> the regex is:
>
> Er, thanks, that confirms my suspicions above :)
>
>
> Antony.
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
 
iQEcBAEBCAAGBQJXYwv7AAoJENNXIZxhPexGn9QH/R2ino1lTfOWrd4E8Z+UUsuH
wjEfi4e96ptkkye57mcOTHXiLgrau+x+vXVS35CNgpwsB3daN1/E6DvAZz/XwABJ
O6/aqIn/JNKmkwLj/XPB0nD0lsrWXoOdknGpL7r/E9un2N2mfAdBVKUbItAuUM+G
DQeKfnRjCDS0Pgt4zlNIQjo0xxSxrjrHThKoWlAi00v2LzWkSmJtbZyW1WtzNbNf
qH8j1LlTbiOg9FmOpp+GVQ8XKEjGnWnhjnydKdVlPr9mXCA6XN5Kn5L6tmckqSc/
Snn9jKZfJAtTg97gTzOJpw9BuGw7pqSRyARcV0/t4PsySNTD/4NpJz/HVKhlT+E=
=Mgx4
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x613DEC46.asc
Type: application/pgp-keys
Size: 2437 bytes
Desc: not available
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20160617/9f0d8a82/attachment.key>