Re: [squid-users] Re: Squid naps each 3600 seconds !
On 26/10/2013 4:28 a.m., Omid Kosari wrote: Alex Rousskov wrote On 10/24/2013 07:43 AM, Omid Kosari wrote: digest_generation off temporary solved problem but needs restart . I have tested with reload before . Sounds like you have detected the source of the blocking Squid problem and confirmed it! The fact that digest generation makes your Squid unresponsive is essentially a Squid bug, but you might be able to help Squid by adjusting its configuration. If you want to try it, I suggest re-enabling digest generation and setting digest_rebuild_chunk_percentage to 1. If that works around your problem, great. Unfortunately, I suspect Squid may still be unresponsive during digest generation time because of how regeneration steps are scheduled and/or because of an old bug in the low-level scheduling code of heavy events. However, using the minimum digest_rebuild_chunk_percentage value (1) is still worth trying. Tried . Unfortunately problem persists . Alex Rousskov wrote But i could not use digest benefits anymore . Is there big penalty if both caches are in same gigabit switch ? The digest optimization can be significant if the two Squids share a lot of popular content _and_ it takes a long time for each Squid to get that content from the internet during a miss. HTH, Alex. I mean if disable digest and just use HTCP . That depends strngly on your traffic level and cache size. HTCP uses bandwidth per-request, but no extra memory and no CPU digesting activity. Digest uses only periodic digest exchange bandwidth, but extra memory and CPU generating the digests. So if you have cache relatively smaller than traffic, digest works better. Low traffic and huge cache size HTCP works better. It will be an interesting study point to graph those and figure out what bandwidth and cache sizes the swapover happens, I dont have anything beyond theory about it though sorry. Amos
[squid-users] Re: Squid naps each 3600 seconds !
Following grabbed from cachemgr.cgi when digest is enabled . May i be sure that digest is not choosed by squid itself and is it safe for me to digest_generation off? Peer Selection Algorithms wrote no guess stats for all peers available Per-peer statistics: peer digest from 1.1.1.12 no guess stats for 1.1.1.12 available event timestamp secs from now secs from init initialized 1382745606 -119863 +0 needed1382745843 -119626 +237 requested 1382822346 -43123 +76740 received 1382822386 -43083 +76780 next_check1382899186 +33717 +153580 peer digest state: needed: yes, usable: no, requested: no last retry delay: 76800 secs last request response time: 40 secs last request result: Forbidden peer digest traffic: requests sent: 9, volume: 0 KB replies recv: 9, volume: 2 KB peer digest structure: no in-memory copy No peer digest from 1.1.1.12 Algorithm usage: Cache Digest: 0 ( 0%) Icp:29887 (100%) Total: 29887 (100%) -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-naps-each-3600-seconds-tp4662811p4662944.html Sent from the Squid - Users mailing list archive at Nabble.com.
Re: [squid-users] Re: Squid naps each 3600 seconds !
On 27/10/2013 10:51 p.m., Omid Kosari wrote: Following grabbed from cachemgr.cgi when digest is enabled . May i be sure that digest is not choosed by squid itself and is it safe for me to digest_generation off? That looks okay. Digests are not being generated or received. Amos Peer Selection Algorithms wrote no guess stats for all peers available Per-peer statistics: peer digest from 1.1.1.12 no guess stats for 1.1.1.12 available event timestamp secs from now secs from init initialized 1382745606 -119863 +0 needed 1382745843 -119626 +237 requested 1382822346 -43123 +76740 received1382822386 -43083 +76780 next_check 1382899186 +33717 +153580 peer digest state: needed: yes, usable: no, requested: no last retry delay: 76800 secs last request response time: 40 secs last request result: Forbidden peer digest traffic: requests sent: 9, volume: 0 KB replies recv: 9, volume: 2 KB peer digest structure: no in-memory copy No peer digest from 1.1.1.12 Algorithm usage: Cache Digest: 0 ( 0%) Icp:29887 (100%) Total: 29887 (100%) -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-naps-each-3600-seconds-tp4662811p4662944.html Sent from the Squid - Users mailing list archive at Nabble.com.
Re: [squid-users] Re: Squid naps each 3600 seconds !
On 10/25/2013 01:22 AM, Alex Rousskov wrote: On 10/24/2013 11:13 AM, Eliezer Croitoru wrote: Out of curiosity, What squid Digest content is? What the Digest rebuild does? Let say an ICP\HTCP request can reflect the Information inside the digest? http://wiki.squid-cache.org/SquidFaq/CacheDigests OK So now we have the other problem: ICP is causing the lookup but it will not so called NAP the squid instance. So we need to see more statistics on this specific digest since it can be a slow HDD or another issues that causes the digest to be very slow. squidclient mgr:store_digest or http://PROXY_IP:FORWARD_PORT/squid-internal-mgr/store_digest; should give more. using the http://PROXY_IP:FORWARD_PORT/squid-internal-mgr/refresh; we should see how is the HTCP\ICP load would be compared to DIGEST. Can you share some more information on this machine Horses ? The above can be a key to identify couple very direct things that results the slow speed of the process. Also regular statistics list of http://PROXY_IP:FORWARD_PORT/squid-internal-mgr/info; can give some more understanding of the situation. Thanks, Eliezer Alex. On 10/24/2013 07:54 PM, Alex Rousskov wrote: On 10/24/2013 07:43 AM, Omid Kosari wrote: digest_generation off temporary solved problem but needs restart . I have tested with reload before . Sounds like you have detected the source of the blocking Squid problem and confirmed it! The fact that digest generation makes your Squid unresponsive is essentially a Squid bug, but you might be able to help Squid by adjusting its configuration. If you want to try it, I suggest re-enabling digest generation and setting digest_rebuild_chunk_percentage to 1. If that works around your problem, great. Unfortunately, I suspect Squid may still be unresponsive during digest generation time because of how regeneration steps are scheduled and/or because of an old bug in the low-level scheduling code of heavy events. However, using the minimum digest_rebuild_chunk_percentage value (1) is still worth trying. But i could not use digest benefits anymore . Is there big penalty if both caches are in same gigabit switch ? The digest optimization can be significant if the two Squids share a lot of popular content _and_ it takes a long time for each Squid to get that content from the internet during a miss. HTH, Alex.
[squid-users] Re: Squid naps each 3600 seconds !
Alex Rousskov wrote On 10/24/2013 07:43 AM, Omid Kosari wrote: digest_generation off temporary solved problem but needs restart . I have tested with reload before . Sounds like you have detected the source of the blocking Squid problem and confirmed it! The fact that digest generation makes your Squid unresponsive is essentially a Squid bug, but you might be able to help Squid by adjusting its configuration. If you want to try it, I suggest re-enabling digest generation and setting digest_rebuild_chunk_percentage to 1. If that works around your problem, great. Unfortunately, I suspect Squid may still be unresponsive during digest generation time because of how regeneration steps are scheduled and/or because of an old bug in the low-level scheduling code of heavy events. However, using the minimum digest_rebuild_chunk_percentage value (1) is still worth trying. Tried . Unfortunately problem persists . Alex Rousskov wrote But i could not use digest benefits anymore . Is there big penalty if both caches are in same gigabit switch ? The digest optimization can be significant if the two Squids share a lot of popular content _and_ it takes a long time for each Squid to get that content from the internet during a miss. HTH, Alex. I mean if disable digest and just use HTCP . -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-naps-each-3600-seconds-tp4662811p4662876.html Sent from the Squid - Users mailing list archive at Nabble.com.
[squid-users] Re: Squid naps each 3600 seconds !
Alex Rousskov wrote On 10/24/2013 07:43 AM, Omid Kosari wrote: digest_generation off temporary solved problem but needs restart . I have tested with reload before . Sounds like you have detected the source of the blocking Squid problem and confirmed it! The fact that digest generation makes your Squid unresponsive is essentially a Squid bug, but you might be able to help Squid by adjusting its configuration. If you want to try it, I suggest re-enabling digest generation and setting digest_rebuild_chunk_percentage to 1. If that works around your problem, great. Unfortunately, I suspect Squid may still be unresponsive during digest generation time because of how regeneration steps are scheduled and/or because of an old bug in the low-level scheduling code of heavy events. However, using the minimum digest_rebuild_chunk_percentage value (1) is still worth trying. Tried . Unfortunately problem persists . Alex Rousskov wrote But i could not use digest benefits anymore . Is there big penalty if both caches are in same gigabit switch ? The digest optimization can be significant if the two Squids share a lot of popular content _and_ it takes a long time for each Squid to get that content from the internet during a miss. HTH, Alex. I mean if disable digest and just use HTCP . -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-naps-each-3600-seconds-tp4662811p4662873.html Sent from the Squid - Users mailing list archive at Nabble.com.
[squid-users] Re: Squid naps each 3600 seconds !
Correction, digest_generation off temporary solved problem but needs restart . I have tested with reload before . But i could not use digest benefits anymore . Is there big penalty if both caches are in same gigabit switch ? -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-naps-each-3600-seconds-tp4662811p4662851.html Sent from the Squid - Users mailing list archive at Nabble.com.
Re: [squid-users] Re: Squid naps each 3600 seconds !
On 10/24/2013 07:43 AM, Omid Kosari wrote: digest_generation off temporary solved problem but needs restart . I have tested with reload before . Sounds like you have detected the source of the blocking Squid problem and confirmed it! The fact that digest generation makes your Squid unresponsive is essentially a Squid bug, but you might be able to help Squid by adjusting its configuration. If you want to try it, I suggest re-enabling digest generation and setting digest_rebuild_chunk_percentage to 1. If that works around your problem, great. Unfortunately, I suspect Squid may still be unresponsive during digest generation time because of how regeneration steps are scheduled and/or because of an old bug in the low-level scheduling code of heavy events. However, using the minimum digest_rebuild_chunk_percentage value (1) is still worth trying. But i could not use digest benefits anymore . Is there big penalty if both caches are in same gigabit switch ? The digest optimization can be significant if the two Squids share a lot of popular content _and_ it takes a long time for each Squid to get that content from the internet during a miss. HTH, Alex.
Re: [squid-users] Re: Squid naps each 3600 seconds !
Out of curiosity, What squid Digest content is? What the Digest rebuild does? Let say an ICP\HTCP request can reflect the Information inside the digest? Thanks, Eliezer On 10/24/2013 07:54 PM, Alex Rousskov wrote: On 10/24/2013 07:43 AM, Omid Kosari wrote: digest_generation off temporary solved problem but needs restart . I have tested with reload before . Sounds like you have detected the source of the blocking Squid problem and confirmed it! The fact that digest generation makes your Squid unresponsive is essentially a Squid bug, but you might be able to help Squid by adjusting its configuration. If you want to try it, I suggest re-enabling digest generation and setting digest_rebuild_chunk_percentage to 1. If that works around your problem, great. Unfortunately, I suspect Squid may still be unresponsive during digest generation time because of how regeneration steps are scheduled and/or because of an old bug in the low-level scheduling code of heavy events. However, using the minimum digest_rebuild_chunk_percentage value (1) is still worth trying. But i could not use digest benefits anymore . Is there big penalty if both caches are in same gigabit switch ? The digest optimization can be significant if the two Squids share a lot of popular content _and_ it takes a long time for each Squid to get that content from the internet during a miss. HTH, Alex.
Re: [squid-users] Re: Squid naps each 3600 seconds !
On 10/24/2013 11:13 AM, Eliezer Croitoru wrote: Out of curiosity, What squid Digest content is? What the Digest rebuild does? Let say an ICP\HTCP request can reflect the Information inside the digest? http://wiki.squid-cache.org/SquidFaq/CacheDigests Alex. On 10/24/2013 07:54 PM, Alex Rousskov wrote: On 10/24/2013 07:43 AM, Omid Kosari wrote: digest_generation off temporary solved problem but needs restart . I have tested with reload before . Sounds like you have detected the source of the blocking Squid problem and confirmed it! The fact that digest generation makes your Squid unresponsive is essentially a Squid bug, but you might be able to help Squid by adjusting its configuration. If you want to try it, I suggest re-enabling digest generation and setting digest_rebuild_chunk_percentage to 1. If that works around your problem, great. Unfortunately, I suspect Squid may still be unresponsive during digest generation time because of how regeneration steps are scheduled and/or because of an old bug in the low-level scheduling code of heavy events. However, using the minimum digest_rebuild_chunk_percentage value (1) is still worth trying. But i could not use digest benefits anymore . Is there big penalty if both caches are in same gigabit switch ? The digest optimization can be significant if the two Squids share a lot of popular content _and_ it takes a long time for each Squid to get that content from the internet during a miss. HTH, Alex.
[squid-users] Re: Squid naps each 3600 seconds !
Unfortunately even the cgi could not get at the time of outage . more investigating shows the disks are completely idle but squid uses 100% cpu . Also i was able to refresh the event 1 second before the time of outage and it shows storeDigestRebuildStart and storeDigestRewriteStart would start 1.438 later . the info part of squid is here because i couldn't find anything . before after -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-naps-each-3600-seconds-tp4662811p4662817.html Sent from the Squid - Users mailing list archive at Nabble.com.
[squid-users] Re: Squid naps each 3600 seconds !
This problem did not occur in 3.1.20 . nothing changed from that version . -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-naps-each-3600-seconds-tp4662811p4662820.html Sent from the Squid - Users mailing list archive at Nabble.com.
Re: [squid-users] Re: Squid naps each 3600 seconds !
On 10/23/2013 04:37 AM, Omid Kosari wrote: Unfortunately even the cgi could not get at the time of outage . more investigating shows the disks are completely idle but squid uses 100% cpu . Also i was able to refresh the event 1 second before the time of outage and it shows storeDigestRebuildStart and storeDigestRewriteStart would start 1.438 later . the info part of squid is here because i couldn't find anything . before after This sounds like a Squid bug to me, but does re-building your Squid with --disable-cache-digests (or without --enable-cache-digests) help? Alex.
[squid-users] Re: Squid naps each 3600 seconds !
Thanks a lot . Is there a way other than compile ? i prefer using http://packages.ubuntu.com/saucy/squid3 Unfortunately digest_generation off does not solve it . -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-naps-each-3600-seconds-tp4662811p4662832.html Sent from the Squid - Users mailing list archive at Nabble.com.
