Re: [squid-users] HDD/RAM Capacity vs store_avg_object_size

2017-07-13 Thread Alex Rousskov
On 07/13/2017 10:17 AM, bugreporter wrote: > But what is this mean value size? Do you have any update to share please? I do not know what value the wiki page authors used, but I suspect it was close to 13K. I believe Amos has already suggested that you use the actual cachable response size mean f

Re: [squid-users] HDD/RAM Capacity vs store_avg_object_size

2017-07-13 Thread bugreporter
Hi Alex, Thank you for your contribution to this post. I see that you answered roughly YES to my question #2. I think that we agree... But what is this mean value size? Do you have any update to share please? According to your answer, HTTP headers are not part of the in-memory index and we have t

Re: [squid-users] HDD/RAM Capacity vs store_avg_object_size

2017-07-13 Thread bugreporter
Hi Amos, When you say: /"The rest is harder. You need to do a scan of a disk cache separating the message headers - both counting the number of items found and total size of the headers processed. Multiplying the metadata size by the number of objects in the cache and adding the total message

Re: [squid-users] HDD/RAM Capacity vs store_avg_object_size

2017-07-13 Thread bugreporter
Hi Amos, Thank you so much for your guidance. You have no idea how the *key* information you shared here is important to me. As your recommendation I'll do my own calculation based on my own cache ASAP. But before doing my own calculation as you answered *No* to my second question, I just wanted

Re: [squid-users] Chaining icap and ecap services - FATAL: Received Segment Violation...dying.

2017-07-13 Thread bugreporter
I can fully understand! Warm Regards, - Bug Reporter Contributor OpenSource = Open-Minded -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Chaining-icap-and-ecap-services-FATAL-Received-Segment-Violation-dying-tp4683033p4683093.html Sent from the Squid - U

Re: [squid-users] Chaining icap and ecap services - FATAL: Received Segment Violation...dying.

2017-07-13 Thread Yuri
Apologies are accepted. No problems. We ourselves were not pleased that we did not have enough time to write the correct and beautiful patch. At that time it was quite an unpleasant problem. The bottom line is that it's very specific and for me it's a big surprise that something similar happened ag

[squid-users] Log to syslog issues with syslog priority

2017-07-13 Thread Peter Viskup
Tried to configure logging to syslog directly and experiencing issues with not accepted syslog priority assigned in config files. This is the configuration: ~# grep -E '^access_log|^icap_log|logstrmfilter' /etc/squid3/squid.conf access_log syslog:local7.notice logformat=combined3 acl logstrmfilter

Re: [squid-users] Chaining icap and ecap services - FATAL: Received Segment Violation...dying.

2017-07-13 Thread bugreporter
Dear Yuri, My goal is not to hurt anybody here and if you consider that I offended you (or rather your "sponsor") I apologize. So sorry! The fact of the matter is that the conversation at http://bugs.squid-cache.org/show_bug.cgi?id=4597 caught my attention and it was the first time I saw such a di