Thanks Alex.
We have a simple cache_dir config like this, with no "workers" defined:
cache_dir rock /cache2 80000 min-size=0 max-size=32767
cache_dir aufs /cache 320000 96 256 min-size=32768
And we are suffering from a 100% CPU use by a single squid thread. We
have lots of ram, cores and disk space.. but also too many users:
Number of clients accessing cache: 1634
Number of HTTP requests received: 3276691
Average HTTP requests per minute since start: 12807.1
Select loop called: 60353401 times, 22.017 ms avg
Getting rid of this big aufs and spreading to many rock stores will
improve things here? I've already shrunk the acls and patterns/regexes etc
Best Regards,
--
Heiler Bemerguy - (91) 98151-4894
Assessor Técnico - CINBESA (91) 3184-1751
Em 23/02/2016 15:20, Alex Rousskov escreveu:
On 02/23/2016 09:15 AM, Heiler Bemerguy wrote:
I'm using Squid Cache: Version 3.5.14 and I'm wondering how big a file
can be on a Rock Store nowardays ?
Is it accepting the full "maximum_object_size" size?
Yes, for large-enough cache_dirs, it should.
AFAIK, there has been no optimization work done for huge files, but they
should be "accepted" by all cache_dir types.
Alex.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
