On Fri, 18 Mar 2011, Amos Jeffries wrote:
On 18/03/11 10:05, da...@lang.hm wrote:
ping, any comments on this?
excluding acl's, cache_peer* and *direct config entries (~500 lines
worth, all IP, servername, port# or url_regex based)
Tested with or without all those ACLs? They do make a
On 18/03/11 21:54, da...@lang.hm wrote:
On Fri, 18 Mar 2011, Amos Jeffries wrote:
snip
Some are offset by optimizations and fixes later, so its not
cut-n-dry. Work is underway by Alex and Co. to identify the problems.
We all work on ways to grab performance back when found. Most of these
cache_log /var/log/squid/cache.log
cache_store_log none
coredump_dir none
no_cache deny all
NP: directive name is just cache.
Hi,
Which directive of these should be just cache in 3.1?
Thanks
Alex
On 18/03/11 22:50, Alex Crow wrote:
cache_log /var/log/squid/cache.log
cache_store_log none
coredump_dir none
no_cache deny all
NP: directive name is just cache.
Hi,
Which directive of these should be just cache in 3.1?
The one which used to be called no_cache back in Squid-2.2.
Hi,
Which directive of these should be just cache in 3.1?
The one which used to be called no_cache back in Squid-2.2.
Amos
So
cache deny all
is the same as
no_cache deny all?
Alex
On Fri, 18 Mar 2011, Amos Jeffries wrote:
On 18/03/11 21:54, da...@lang.hm wrote:
On Fri, 18 Mar 2011, Amos Jeffries wrote:
snip
Some are offset by optimizations and fixes later, so its not
cut-n-dry. Work is underway by Alex and Co. to identify the problems.
We all work on ways to grab
On Fri, 18 Mar 2011, da...@lang.hm wrote:
On Fri, 18 Mar 2011, Amos Jeffries wrote:
On 18/03/11 10:05, da...@lang.hm wrote:
ping, any comments on this?
excluding acl's, cache_peer* and *direct config entries (~500 lines
worth, all IP, servername, port# or url_regex based)
Tested with or
On 19/03/11 04:32, Alex Crow wrote:
Hi,
Which directive of these should be just cache in 3.1?
The one which used to be called no_cache back in Squid-2.2.
Amos
So
cache deny all
is the same as
no_cache deny all?
Yes. They are identical, except that recently Squid will throw warnings
On 19/03/11 10:44, da...@lang.hm wrote:
On Fri, 18 Mar 2011, Amos Jeffries wrote:
On 18/03/11 21:54, da...@lang.hm wrote:
On Fri, 18 Mar 2011, Amos Jeffries wrote:
snip
Some are offset by optimizations and fixes later, so its not
cut-n-dry. Work is underway by Alex and Co. to identify the
On 19/03/11 10:53, da...@lang.hm wrote:
On Fri, 18 Mar 2011, da...@lang.hm wrote:
On Fri, 18 Mar 2011, Amos Jeffries wrote:
On 18/03/11 10:05, da...@lang.hm wrote:
ping, any comments on this?
excluding acl's, cache_peer* and *direct config entries (~500 lines
worth, all IP, servername,
ping, any comments on this?
excluding acl's, cache_peer* and *direct config entries (~500 lines
worth, all IP, servername, port# or url_regex based)
the remaining config file is
http_port 8000
icp_port 0
visible_hostname gromit1
cache_effective_user proxy
cache_effective_group proxy
On 18/03/11 10:05, da...@lang.hm wrote:
ping, any comments on this?
excluding acl's, cache_peer* and *direct config entries (~500 lines
worth, all IP, servername, port# or url_regex based)
Tested with or without all those ACLs? They do make a difference to
speed, even the fast ACL tests.
I'm using squid in a pure access control mode (all caching disabled) and
am looking to move from 3.0 to 3.1, but when I'm doing lab tests with it I
am seeing a significant performance drop.
when doing a simple small request test (using ab to hammer the proxy
retrieving 40 byte pages) 3.0 is
13 matches
Mail list logo
