<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">14.11.2016 21:59, Eduardo Carneiro
пишет:<br>
</div>
<blockquote cite="mid:1479139166591-4680490.post@n4.nabble.com"
type="cite">
<pre wrap="">Yuri Voinov wrote
</pre>
<blockquote type="cite">
<pre wrap=""><a class="moz-txt-link-freetext" href="http://wiki.squid-cache.org/Features/SmpScale">http://wiki.squid-cache.org/Features/SmpScale</a>
<a class="moz-txt-link-freetext" href="http://wiki.squid-cache.org/MultipleInstances">http://wiki.squid-cache.org/MultipleInstances</a>
14.11.2016 20:22, Eduardo Carneiro пишет:
</pre>
<blockquote type="cite">
<pre wrap="">Hi everyone!
I have a Squid 3.5.19 with dynamic content cache using url rewrite. It's
a
virtual machine (VMWare) with 2 quad-core processors each. Squid proccess
is
100% in one of my eight cores and the access it's getting very slow.
There exists any way to compile squid with multithread option? The idea
is
spread this processing beetwen the 8 cores.
Thanks.
--
View this message in context:
<a class="moz-txt-link-freetext" href="http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-multithread-tp4680488.html">http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-multithread-tp4680488.html</a>
Sent from the Squid - Users mailing list archive at Nabble.com.
_______________________________________________
squid-users mailing list
</pre>
</blockquote>
</blockquote>
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap=""><a class="moz-txt-link-abbreviated" href="mailto:squid-users@.squid-cache">squid-users@.squid-cache</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""><a class="moz-txt-link-freetext" href="http://lists.squid-cache.org/listinfo/squid-users">http://lists.squid-cache.org/listinfo/squid-users</a>
</pre>
</blockquote>
<pre wrap="">
--
Cats - delicious. You just do not know how to cook them.
_______________________________________________
squid-users mailing list
</pre>
</blockquote>
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap=""><a class="moz-txt-link-abbreviated" href="mailto:squid-users@.squid-cache">squid-users@.squid-cache</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap=""><a class="moz-txt-link-freetext" href="http://lists.squid-cache.org/listinfo/squid-users">http://lists.squid-cache.org/listinfo/squid-users</a>
0x613DEC46.asc (2K)
<<a class="moz-txt-link-freetext" href="http://squid-web-proxy-cache.1019090.n4.nabble.com/attachment/4680489/0/0x613DEC46.asc>">http://squid-web-proxy-cache.1019090.n4.nabble.com/attachment/4680489/0/0x613DEC46.asc></a>;
signature.asc (484 bytes)
<<a class="moz-txt-link-freetext" href="http://squid-web-proxy-cache.1019090.n4.nabble.com/attachment/4680489/1/signature.asc>">http://squid-web-proxy-cache.1019090.n4.nabble.com/attachment/4680489/1/signature.asc></a>;
</pre>
</blockquote>
<pre wrap="">
From what I understood I will need to use each instance in different ports,
right? This does not solve my problem. There are any way to separate one
instance for accesses and another for cache?</pre>
</blockquote>
<br>
<h3 id="What_can_workers_share.3F" style="margin: 1.5em 0px 0px;
padding: 0px 0px 0.3em; color: rgb(0, 0, 0); border-bottom: 2px
solid rgb(0, 0, 153); line-height: 1.2em; font-size: 1.3em;
font-family: Arial, "Lucida Grande", sans-serif;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255);">What can workers share?</h3>
<span class="anchor" id="line-60" style="color: rgb(0, 0, 0);
font-family: Arial, "Lucida Grande", sans-serif;
font-size: 13.6px; font-style: normal; font-variant-ligatures:
normal; font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; orphans: 2; text-align: start;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);"></span><span class="anchor"
id="line-61" style="color: rgb(0, 0, 0); font-family: Arial,
"Lucida Grande", sans-serif; font-size: 13.6px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: normal; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);"></span>
<p class="line874" style="color: rgb(0, 0, 0); font-family: Arial,
"Lucida Grande", sans-serif; font-size: 13.6px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: normal; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">Using Coordinator and
common configuration files, Squid workers can receive identical
configuration information and synchronize some of their
activities. By default, Squid workers share the following:<span
class="Apple-converted-space"> </span><span class="anchor"
id="line-62"></span><span class="anchor" id="line-63"></span></p>
<ul style="color: rgb(0, 0, 0); font-family: Arial, "Lucida
Grande", sans-serif; font-size: 13.6px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255);">
<li>Squid executable,<span class="Apple-converted-space"> </span><span
class="anchor" id="line-64"></span></li>
<li>general configuration,<span class="Apple-converted-space"> </span><span
class="anchor" id="line-65"></span></li>
<li>listening ports (but shared ICP and HTCP ports do not work
well; see below),<span class="Apple-converted-space"> </span><span
class="anchor" id="line-66"></span></li>
<li>logs,<span class="Apple-converted-space"> </span><span
class="anchor" id="line-67"></span></li>
<li>memory object cache (in most environments),<span
class="Apple-converted-space"> </span><span class="anchor"
id="line-68"></span></li>
<li>disk object cache (with Rock Store only),<span
class="Apple-converted-space"> </span><span class="anchor"
id="line-69"></span></li>
<li>
<p class="line862" style="margin: 0.25em 0px;">insecure cache
manager statistics (detailed<span
class="Apple-converted-space"> </span><a
href="http://wiki.squid-cache.org/Features/CacheManager#SMP_considerations"
style="color: rgb(89, 123, 179); border: 0px;">elsewhere</a>),<span
class="Apple-converted-space"> </span><span class="anchor"
id="line-70"></span></p>
</li>
<li>SNMP statistics.<span class="Apple-converted-space"> <br>
</span></li>
</ul>
<p class="line874" style="color: rgb(0, 0, 0); font-family: Arial,
"Lucida Grande", sans-serif; font-size: 13.6px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: normal; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">Cache indexes are shared
without copying. Other shared information is usually small in
terms of RAM use and is essentially copied to avoid locking and
associated performance overheads.<span
class="Apple-converted-space"> </span><span class="anchor"
id="line-73"></span><span class="anchor" id="line-74"></span></p>
<p class="line874" style="color: rgb(0, 0, 0); font-family: Arial,
"Lucida Grande", sans-serif; font-size: 13.6px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: normal; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">Conditional configuration
and worker-dependent macros can be used to limit sharing. For
example, each worker can be given a dedicated http_port to listen
on.<span class="Apple-converted-space"> </span><span
class="anchor" id="line-75"></span><span class="anchor"
id="line-76"></span><span class="anchor" id="line-77"></span></p>
<p class="line874" style="color: rgb(0, 0, 0); font-family: Arial,
"Lucida Grande", sans-serif; font-size: 13.6px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: normal; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">Currently, Squid workers do
not share and do not synchronize other resources and services,
including (but not limited to):<span class="Apple-converted-space"> </span><span
class="anchor" id="line-78"></span><span class="anchor"
id="line-79"></span></p>
<ul style="color: rgb(0, 0, 0); font-family: Arial, "Lucida
Grande", sans-serif; font-size: 13.6px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255);">
<li>memory object cache (in some environments),<span
class="Apple-converted-space"> </span><span class="anchor"
id="line-80"></span></li>
<li>disk object cache (except for Rock Store),<span
class="Apple-converted-space"> </span><span class="anchor"
id="line-81"></span></li>
<li>DNS caches (ipcache and fqdncache),<span
class="Apple-converted-space"> </span><span class="anchor"
id="line-82"></span></li>
<li>helper processes and daemons,<span
class="Apple-converted-space"> </span><span class="anchor"
id="line-83"></span></li>
<li>
<p class="line862" style="margin: 0.25em 0px;">stateful HTTP
authentication (e.g., digest authentication; see bug<span
class="Apple-converted-space"> </span><a class="http"
href="http://bugs.squid-cache.org/show_bug.cgi?id=3517"
style="color: rgb(89, 123, 179); border: 0px;">3517</a>),<span
class="Apple-converted-space"> </span><span class="anchor"
id="line-84"></span></p>
</li>
<li>delay pools,<span class="Apple-converted-space"> </span><span
class="anchor" id="line-85"></span></li>
<li>SSL session cache (there is an active project to allow session
sharing among workers),<span class="Apple-converted-space"> </span><span
class="anchor" id="line-86"></span></li>
<li>
<p class="line862" style="margin: 0.25em 0px;">secure cache
manager statistics (detailed<span
class="Apple-converted-space"> </span><a
href="http://wiki.squid-cache.org/Features/CacheManager#SMP_considerations"
style="color: rgb(89, 123, 179); border: 0px;">elsewhere</a>),<span
class="Apple-converted-space"> </span><span class="anchor"
id="line-87"></span></p>
</li>
<li>
<p class="line862" style="margin: 0.25em 0px;">ICP/HTCP (works
with a caveat: If multiple workers share the same ICP/HTCP
port, an ICP/HTCP response may not go the worker that sent the
request, causing timeouts at the requesting worker; use a
dedicated ICP/HTCP port as a<span
class="Apple-converted-space"> </span><a class="http"
href="http://www.squid-cache.org/mail-archive/squid-users/201308/0358.html"
style="color: rgb(89, 123, 179); border: 0px;">workaround</a>).<span
class="Apple-converted-space"> </span><span class="anchor"
id="line-88"></span><span class="anchor" id="line-89"></span></p>
</li>
</ul>
<p class="line874" style="color: rgb(0, 0, 0); font-family: Arial,
"Lucida Grande", sans-serif; font-size: 13.6px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: normal; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">Some SMP-unaware features
continue to work in SMP mode (e.g., DNS responses are going to be
cached by individual workers), but their performance suffers from
the lack of synchronization and they require more resources due to
duplication of information (e.g., each worker may independently
resolve and cache the IP of the same domain name). Some
SMP-unaware features break badly (e.g., ufs-based cache_dirs
become corrupted) unless squid.conf conditionals are used to
prevent such breakage. Some SMP-unaware features will appear to
work but will do so incorrectly (e.g., delay pools will limit
bandwidth on per-worker basis, without sharing traffic information
among workers and without dividing bandwidth limits among
workers).<span class="Apple-converted-space"> <br>
</span></p>
<blockquote cite="mid:1479139166591-4680490.post@n4.nabble.com"
type="cite">
<pre wrap="">
--
View this message in context: <a class="moz-txt-link-freetext" href="http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-multithread-tp4680488p4680490.html">http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-multithread-tp4680488p4680490.html</a>
Sent from the Squid - Users mailing list archive at Nabble.com.
_______________________________________________
squid-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a>
<a class="moz-txt-link-freetext" href="http://lists.squid-cache.org/listinfo/squid-users">http://lists.squid-cache.org/listinfo/squid-users</a>
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
Cats - delicious. You just do not know how to cook them.</div>
</body>
</html>