#583730 calamaris: Byte hit ratio is IMHO calculated wrong for Squid 3

Package:
calamaris
Source:
calamaris
Submitter:
wondra
Date:
2015-06-30 18:12:24 UTC
Severity:
wishlist
#583730#5
Date:
2010-05-30 08:39:04 UTC
From:
To:
After the change in refresh hit/miss tags from Squid 2 to 3, all refresh tags are counted as MISS, whereas before TCP_IMS_HIT was counted as HIT.
I think the best behavior would be to count TCP_REFRESH_MISS as MISS and TCP_REFRESH_HIT as request MISS and byte HIT.
Could you modify Calamaris to enable the user to configure which tags count as hits and misses for the request and byte statistics separately?
Thanks, wondra
#583730#10
Date:
2015-06-30 10:47:06 UTC
From:
To:
Hallo,

I just came over your Bugreport, as I revived the project.

I can't see that all TCP_REFRESH-Requests are counted as MISS:

# Incoming TCP-requests by status
status                          request      %  sec/req   Byte       %  kB/sec
------------------------------ --------- ------ ------- -------- ------ ------- 
HIT                                  994  60.57    1.91  2383734  36.43    1.23
 TCP_REFRESH_HIT                     994  60.57    1.91  2383734  36.43    1.23
MISS                                 645  39.31    3.37  4159659  63.57    1.87
 TCP_REFRESH_MISS                    645  39.31    3.37  4159659  63.57    1.87
ERROR                                  2   0.12  103.01        0   0.00    0.00
 TCP_REFRESH_MISS                      2   0.12  103.01        0   0.00    0.00
------------------------------ --------- ------ ------- -------- ------ ------- 
Sum                                 1641 100.00    2.60  6543393 100.00    1.50

Could you send me a few lines of your Squidlog?

Cord
#583730#15
Date:
2015-06-30 11:46:12 UTC
From:
To:
Hi!
Glad to hear that you'll maintain the project. I'm running it for I don't know how many years. But that also means I'm probably running an outdated version. I'm still on Debian squeeze. Squid version 3.1.6, Calamaris 2.99.4. What are your versions? The proxy serves my home network and also caches my private server. My report looks like this:

# Incoming TCP-requests by status
status                          request      %  sec/req   Byte       %  kB/sec
------------------------------ --------- ------ ------- -------- ------ ------- 
HIT                                 8452   8.83    1.08 28738294   1.62    3.08
 TCP_IMS_HIT                        4964   5.18    0.03  1708831   0.10   12.95
 TCP_HIT                            2921   3.05    3.06 25519797   1.44    2.79
 TCP_MEM_HIT                         567   0.59    0.06  1509666   0.08   42.09
MISS                               82363  86.01   12.85 1698055K  97.78    1.60
 TCP_MISS                          77113  80.53   13.48 1676552K  96.55    1.61
 TCP_REFRESH_UNMODIFIED             4058   4.24    3.44 13834904   0.78    0.97
 TCP_CLIENT_REFRESH_MISS             612   0.64    3.47  5654370   0.32    2.60
 TCP_REFRESH_MODIFIED                563   0.59    3.08  2419832   0.14    1.36
 TCP_REFRESH_FAIL                     15   0.02   77.59    95146   0.01    0.08
 TCP_SWAPFAIL_MISS                     2   0.00    0.43    15126   0.00   17.24
ERROR                               4945   5.16    0.05 10669423   0.60   42.43
 TCP_DENIED                         4932   5.15    0.01  1945507   0.11   59.04
 TCP_MISS                             13   0.01   16.41  8723916   0.49   39.93
------------------------------ --------- ------ ------- -------- ------ ------- 
Sum                                95760 100.00   11.15 1736539K 100.00    1.63

There are different codes for TCP_REFRESH. Probably the bug is made obsolete by some change in Squid.
Tomas
#583730#20
Date:
2015-06-30 18:04:28 UTC
From:
To:
Hallo! Du (Tomas Vondra) hast geschrieben:

2.99.4.2 is the latest. Main feature is Squid3.3-compatibility, you
should not be affected as long as you stay on Squid 3.1

So i can close this bug as 'unreproducable'?

Cord