[squid-users] doubt in how squid works with cache

From: spiderslack <spiderslack_at_yahoo.com.br>
Date: Tue, 18 Feb 2014 13:25:45 -0400

Hi all.

i am trying to do web squid store any content, compiled squid 3.4 and
I'm auditioning. The first test is the desire of many network
administrators do youtube cache. After some tests the cache was not done
the youtube video then panned the html the following
videohttps://www.youtube.com/watch?v=KaI8sdDxCAc .it possesses 11
seconds to test everything and not spend time waiting for the video 1
hour eg load. After panning with wireshark the html found true URL
https://youtube.googleapis.com/v/KaI8sdDxCAc?autohide=1&amp=&version=3 .
The video opens fullscreen in firefox. But to take the test by
monitoring the access.log I see q he does not cache. I did the accessing
of a computer with IP address 192.168.1.104 did 2 test request he made
the first storing far so good because the content was not in the cache,
but the second request he continued giving TCP_MISS

first request
1392741947.876 50655 192.168.1.104 TCP_MISS/200 4839 CONNECT
youtube.googleapis.com:443 - HIER_DIRECT/74.125.196.95 -
1392741947.876 50655 192.168.1.104 TCP_MISS/200 4839 CONNECT
youtube.googleapis.com:443 - HIER_DIRECT/74.125.196.95 -
1392741954.058 1868 192.168.1.104 TCP_MISS/200 191067 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392741954.058 1868 192.168.1.104 TCP_MISS/200 191067 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392741957.880 192 192.168.1.104 TCP_MISS/200 8191 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392741957.880 192 192.168.1.104 TCP_MISS/200 8191 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392741960.315 8123 192.168.1.104 TCP_MISS_ABORTED/200 765472 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392741960.315 8123 192.168.1.104 TCP_MISS_ABORTED/200 765472 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392741960.696 380 192.168.1.104 TCP_MISS/200 42829 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392741960.696 380 192.168.1.104 TCP_MISS/200 42829 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392741960.723 408 192.168.1.104 TCP_MISS/200 31464 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392741960.723 408 192.168.1.104 TCP_MISS/200 31464 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream

second request
1392742008.148 60272 192.168.1.104 TCP_MISS/200 4834 CONNECT
youtube.googleapis.com:443 - HIER_DIRECT/74.125.196.95 -
1392742008.148 60272 192.168.1.104 TCP_MISS/200 4834 CONNECT
youtube.googleapis.com:443 - HIER_DIRECT/74.125.196.95 -
1392742013.610 2082 192.168.1.104 TCP_MISS/200 191067 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392742013.610 2082 192.168.1.104 TCP_MISS/200 191067 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392742017.411 97 192.168.1.104 TCP_MISS_ABORTED/200 6270 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392742017.411 97 192.168.1.104 TCP_MISS_ABORTED/200 6270 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392742020.215 8687 192.168.1.104 TCP_MISS_ABORTED/200 766932 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392742020.215 8687 192.168.1.104 TCP_MISS_ABORTED/200 766932 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392742021.253 1039 192.168.1.104 TCP_MISS/200 42829 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392742021.253 1039 192.168.1.104 TCP_MISS/200 42829 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392742021.696 1484 192.168.1.104 TCP_MISS/200 31464 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392742021.696 1484 192.168.1.104 TCP_MISS/200 31464 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392742026.135 197 192.168.1.104 TCP_MISS/200 22229 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392742026.135 197 192.168.1.104 TCP_MISS/200 22229 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392742029.418 5438 192.168.1.104 TCP_MISS/200 7821 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream
1392742029.418 5438 192.168.1.104 TCP_MISS/200 7821 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback? -
HIER_DIRECT/200.172.62.13 application/octet-stream

both request not cached. I analyzed the file Store.log

1392741960.696 RELEASE -1 FFFFFFFF 74383CA3759991724913BB167AA6A00B 200
1392741960 1391952665 1392765831 application/octet-stream 42398/42398
GEThttp://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback?
1392741960.723 RELEASE -1 FFFFFFFF D74EF1C72972349C2635B7052D7E531F 200
1392741960 1391952657 1392765831 application/octet-stream 31033/31033
GEThttp://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback?
1392742013.610 RELEASE -1 FFFFFFFF 55A610CC7092326D0635549D906B2B1D 200
1392742011 1391952657 1392765831 application/octet-stream 190635/190635
GEThttp://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback?
1392742017.411 RELEASE -1 FFFFFFFF A986E09468B67937776A5A2212D490C1 200
1392742017 1391952665 1392765831 application/octet-stream 7761/-364 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback?
1392742020.215 RELEASE -1 FFFFFFFF 44A176DC3509059038E93464C768B8A9 200
1392742011 1391952679 1392765831 application/octet-stream 806567/-371
GEThttp://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback?
1392742021.253 RELEASE -1 FFFFFFFF 4162C09C64920C22666A047A49650722 200
1392742020 1391952665 1392765831 application/octet-stream 42398/42398
GEThttp://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback?
1392742021.696 RELEASE -1 FFFFFFFF FCA0019946D0C6CA3F6ECFDD32B8C5B1 200
1392742020 1391952657 1392765831 application/octet-stream 31033/31033
GEThttp://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback?
1392742026.135 RELEASE -1 FFFFFFFF 68D958248AD1EAD961247D72E9E5AFE8 200
1392742025 1391952668 1392765831 application/octet-stream 21798/21798
GEThttp://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback?
1392742029.418 RELEASE -1 FFFFFFFF 9FBB860ED30BDFC22CED2ABD6D180028 200
1392742023 1391952668 1392765831 application/octet-stream 7391/7391 GET
http://r2---sn-xhcg5uxa-bpbe.googlevideo.com/videoplayback?

According squid documentation fields Store.log file are defined at the
site.http://wiki.squid-cache.org/SquidFaq/SquidLogs#store.log

What intrigued me is the field action, dir number and file number.
RELEASE code to say that the object was removed from the cache (?? Ham
as it was removed if it was not for caching) dir_number says that the
cache directory was stored in the -1 and consistent because it was not
stored then - 1 (error) now says that the line number FFFFFFFF code
indicates that the object is in memory. Well so far so good, but if this
in mind because in access.log showed me a TCP_MEM_HIT rather than
TCP_MISS. According to my maximum_object_in_memory this parameter as
64KB and video according to the log must be 7391 or 7K, I'm right, all
right until the object has to be in memory because the code then
continues TCP_MISS not the TCP_MEM_HIT? has anyone ever experienced this?

Regards.
Received on Tue Feb 18 2014 - 17:21:03 MST

This archive was generated by hypermail 2.2.0 : Wed Feb 19 2014 - 12:00:06 MST