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
appaend_domain .invalid.server.name
pid_filename /var/run/squid.pid
cache_dir null /tmp
client_db off
cache_access_log syslog squid
cache_log /var/log/squid/cache.log
cache_store_log none
coredump_dir none
no_cache deny all
what would I need to do to track down the cause of this performance drop?
David Lang
On Sun, 13 Mar 2011, david@xxxxxxx wrote:
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 reaching 4200 request/sec while under the
exact same conditions 3.1.11 is barely topping 1400 requests/sec.
if I request larger pages (100K), 3.0 does ~650 requests/sec while 3.1 only
manages ~480 requests/sec. going up to 1M pagess, 3.0 does 90 requests/sec
while 3.1 does 60
this is with identical configuration except that 3.0 has the null disk cache
driver configured while 3.1 has that line commented out.
In all of these cases, squid is maxing out at 100% of the single core it has
available to it.
David Lang
