> > > I understand that Amos is eager to get more tests and more results about > the latest enhancements, but as Amos himself also stated earlier, please > use a released version of Squid for testing since the test results for > 3.3.x or 3.4.x are interesting for admins of Squid who can consider > upgrading, > but test results for 3.HEAD are not useful for them since they are not > likely > to consider an upgrade to 3.HEAD. > > And if you have spare resources, it would be interesting to perform the > same test for 3.3.5 and 3.2.11 to see the differences between releases. > And of course, when 3.4 comes out, perform the test again... > > The test that you performed is very nice. I am sure that many like this. > But I also like to see the full squid.conf. Just for transparency and > maybe to suggest an optimisation tweak. > Here is my squid conf: I am using squid as a normal forward proxy with SSL bump. You would be able to see that I have not tampered with the memory_pools or ssl_session much. *****************SQUID.CONF********************************** cache_effective_user madmin always_direct allow all ssl_bump allow all sslproxy_cert_error allow all sslproxy_flags DONT_VERIFY_PEER # No need for caching cache deny all #Dont need logs for benchmarks access_log none # SMP scale workers 8 # Turn off ICAP for the benchmarks icap_enable off #Only for benchmarks http_access allow all # Dynamic certificate generation sslcrtd_program /usr/local/squid-3.3/libexec/ssl_crtd -s /usr/local/squid-3.3/var/lib/ssl_db -M 4MB sslcrtd_children 10 #PORTS http_port 10.174.198.149:3128 ssl-bump generate-host-certificates=on dynamic_cert_mem_cache_size=4MB cert=/home/madmin/squid/ca.pem key=/home/madmin/squid/ca.pem https_port 10.174.198.149:3129 ssl-bump generate-host-certificates=on dynamic_cert_mem_cache_size=4MB cert=/home/madmin/squid/ca.pem key=/home/madmin/squid/ca.pem ****************************************************************** > Thanks > Marcus -- Regards, -Ahmed Talha Khan
