[squid-users] Unable to get TCP_MEM_HIT (just TCP_HIT) with rock storage

[Eliezer Croitoru]

Hey,

It's not clear to me if the issue you are trying to resolve is for a specific service or squid-wide.
Your tests are done on localhost so it might reflect other services as well but still I want to be sure I understand what you are aiming for.
If you are indeed aiming a specific service then I believe that your setup+squid.conf maybe not what you need.

Eliezer

----
Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: eliezer at ngtech.co.il


-----Original Message-----
From: squid-users [mailto:squid-users-bounces at lists.squid-cache.org] On Behalf Of duanyao
Sent: Tuesday, October 17, 2017 07:31
To: squid-users at lists.squid-cache.org
Subject: [squid-users] Unable to get TCP_MEM_HIT (just TCP_HIT) with rock storage

Hi,

When I test squid with rock storage, I have never got a TCP_MEM_HIT 
(just TCP_HIT) in access.log. I do get TCP_MEM_HIT with ufs storage.

Is this normal, or something is mis-configured?


I run squid locally, and run `curl -v -x localhost:3128 
http://localhost:8001/1000 > /dev/null` two times successively, and 
expect at least the second one being TCP_MEM_HIT, but it is always TCP_HIT.


Attachment "squid.conf" is my configuration file; and "cache.rock.log" 
is the part of cache.log during 2 successive accesses to a same URL; 
"anysize-server.js" is the HTTP server at port 8001 for the test, and 
you can run it by `node anysize-server.js`.


I tested squid 3.5.27 and 4.0.21, both compiled and run on Linux x86_64: 
`./configure --with-default-user=duanyao 
--prefix=/home/duanyao/project/proxy/squid-root/`.


Thanks.


Duan, Yao