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

Hi, FYI I had the same object (an image) duplicated x1000, x1, x3, x6, x10, x13, x16 and finally x20. The real size of my object was ~ 45 KB (48 KB for squid as in counts headers + fs structure I guess). The growth was almost linear and values I posted here is an avera

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

Hi Alex & Amos. Below results: On a x64 machine: v ~ 207 Bytes On a x86 machine: v ~ 116 Warm Regards, - Bug Reporter Contributor OpenSource = Open-Minded -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/HDD-RAM-Capacity-vs-store-avg-object-size-tp46830

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

Thank you Amos, OK so how can I accurately measure the memory usage? Kind Regards, - Bug Reporter Contributor OpenSource = Open-Minded -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/HDD-RAM-Capacity-vs-store-avg-object-size-tp4683072p4683116.html Sent

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

Hi, Thank you for this clarification. Can you please tell me what is the best method to measure the RAM used by Squid? Can I trust *top* and/or *ps* and look at the RSS? Or you suggest another method (maybe using the manager)? For instance on a 64x when I start squid without cache_dir and a cache

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

Hi Alex, By doing so I'll get a new (or the same) rough estimation which is not what I'm really looking for. Actually I need to have a formula based on the mean object size so I can periodically (with a cron) get the mean object size and with the help of that formula reconfigure Squid accordingly.

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

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

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

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.

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.

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

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

Hi Antony, If they effectively don't *distribute* their modifications... But we don't know. Thank you so much for the clarification. Kind Regards, - Bug Reporter Contributor OpenSource = Open-Minded -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Chaini

[squid-users] HDD/RAM Capacity vs store_avg_object_size

Hi, Can anybody help me to confirm my understanding of the memory usage vs the persistent cache capacity? Below my understanding: According to http://wiki.squid-cache.org/SquidFaq/SquidMemory: 1- We need 14 MB of memory per 1 GB on disk for 64-bit Squid.The wiki is there since I know squid (ie.

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

Hi Alex, Thank you for your post. I do appreciate your help and recommendations. By chance, do you know another adapter that I can use to replace squid-ecap-gzip. Actually I'm looking for an adapter capable to compress HTTP contents. Warm Reagrds, - Bug Reporter Contributor OpenSource =

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

Thank you Yuri, The least I can say is that the conversation at http://bugs.squid-cache.org/show_bug.cgi?id=4597 makes me laugh a lot. My opinion is that if you modify the source code of an open source program without publishing your modifications your are in contradiction with GPL v2. Your sponso

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

Hi Yuri , Below the gdb backtrace. I hope that it could help you resolving the issue. Regarding Squid-4.0 my understanding is that it is a beta version while I need a stable version. Actually at this stage upgrading to 4.0 would represent a lot of integration, testing and validation work. Therefo

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

And the gd backtrace: 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-tp4683033p4683040.html Sent from the Squid

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

Yes I had some issue with ecap-gzip (related to chunked content) that I have already resolved by bypassing chunked content (I modified the code). Now I have no issue with ecap-gzip when it's used alone (without being in a chain). Herewith the log file (debug_options ALL,3): squid.gz

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

Thank you for your prompt response Yuri. Below information that you have requested: - Squid 3.5.26 - Linux kernel 3.10.100 on an LFS (Linux From Scratch) - gcc-4.8.1, glibc-2.18 Don't yet have a core dump. Are you interested in having the log file in debug mode? Cheers - Bug Reporter Contr

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

Hi, Is it allowed (supported) to chain icap and ecap services (using /adaptation_service_chain/)? I get a "FATAL: Received Segment Violation...dying." when trying to do it with some websites (www.linguee.com for instance). Each of those services works very well separately. Maybe this has never be