
 
<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments for IScale</title>
	<atom:link href="http://dotimes.com/iscale/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://dotimes.com/iscale</link>
	<description>Yet Another Weblog on Open Source Appliance</description>
	<pubDate>Wed, 20 Aug 2008 18:29:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>Comment on Packaging Varnish for Slackware by Normison.</title>
		<link>http://dotimes.com/iscale/2007/12/packaging-varnish-for-slackware.html#comment-550</link>
		<dc:creator>Normison.</dc:creator>
		<pubDate>Sat, 05 Jul 2008 23:07:32 +0000</pubDate>
		<guid isPermaLink="false">http://dotimes.com/iscale/2007/12/packaging-varnish-for-slackware.html#comment-550</guid>
		<description>&lt;strong&gt;Normison....&lt;/strong&gt;

Normison....</description>
		<content:encoded><![CDATA[<p><strong>Normison&#8230;.</strong></p>
<p>Normison&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Packaging Varnish for Slackware by Xanax.</title>
		<link>http://dotimes.com/iscale/2007/12/packaging-varnish-for-slackware.html#comment-186</link>
		<dc:creator>Xanax.</dc:creator>
		<pubDate>Mon, 19 May 2008 12:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://dotimes.com/iscale/2007/12/packaging-varnish-for-slackware.html#comment-186</guid>
		<description>&lt;strong&gt;Xanax....&lt;/strong&gt;

Xanax....</description>
		<content:encoded><![CDATA[<p><strong>Xanax&#8230;.</strong></p>
<p>Xanax&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Packaging Varnish for Slackware by Viagra.</title>
		<link>http://dotimes.com/iscale/2007/12/packaging-varnish-for-slackware.html#comment-168</link>
		<dc:creator>Viagra.</dc:creator>
		<pubDate>Fri, 16 May 2008 17:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://dotimes.com/iscale/2007/12/packaging-varnish-for-slackware.html#comment-168</guid>
		<description>&lt;strong&gt;Buy cheap viagra online uk....&lt;/strong&gt;

Viagra. Viagra dosage. Order viagra. Viagra buy. Generic viagra. Free viagra. Best price on viagra....</description>
		<content:encoded><![CDATA[<p><strong>Buy cheap viagra online uk&#8230;.</strong></p>
<p>Viagra. Viagra dosage. Order viagra. Viagra buy. Generic viagra. Free viagra. Best price on viagra&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Benchmark Caching of Varnish and Squid by Cherife Li</title>
		<link>http://dotimes.com/iscale/2008/03/benchmark-caching-of-varnish-and-squid.html#comment-99</link>
		<dc:creator>Cherife Li</dc:creator>
		<pubDate>Fri, 18 Apr 2008 07:38:49 +0000</pubDate>
		<guid isPermaLink="false">http://dotimes.com/iscale/2008/03/benchmark-caching-of-varnish-and-squid.html#comment-99</guid>
		<description>[Comment ID #98 Will Be Quoted Here]
Really? Never heard before.
It's appreciate if you could give your benchmark results(maybe a link?). Although most benchmark results  is just for *reference*, which is not from real life.

BTW: I just have a *feel* that Nginx is faster than Lighttpd in production, according to my experience.</description>
		<content:encoded><![CDATA[<blockquote class='comment_quote'><p><a href="http://dotimes.com/iscale/2008/03/benchmark-caching-of-varnish-and-squid.html#comment-98" title="Click here to view the original comment"><em>Enzo on Fri, 18 Apr 2008 at 12:46 said:</em></a></p>
<p>The odd thing when I benchmarked Lighttpd, Lighttpd + Squid, and Lighttpd + Varnish, Lighttpd all by itself turned out to be faster than either reverse proxy plus Lighttpd.   I was benchmarking with ab, not sure if that made any difference.</p>
<p>I wasn&#8217;t expecting lighttpd by itself to be faster though.</p></blockquote>
<p>Really? Never heard before.<br />
It&#8217;s appreciate if you could give your benchmark results(maybe a link?). Although most benchmark results  is just for *reference*, which is not from real life.</p>
<p>BTW: I just have a *feel* that Nginx is faster than Lighttpd in production, according to my experience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Benchmark Caching of Varnish and Squid by Enzo</title>
		<link>http://dotimes.com/iscale/2008/03/benchmark-caching-of-varnish-and-squid.html#comment-98</link>
		<dc:creator>Enzo</dc:creator>
		<pubDate>Fri, 18 Apr 2008 04:46:29 +0000</pubDate>
		<guid isPermaLink="false">http://dotimes.com/iscale/2008/03/benchmark-caching-of-varnish-and-squid.html#comment-98</guid>
		<description>The odd thing when I benchmarked Lighttpd, Lighttpd + Squid, and Lighttpd + Varnish, Lighttpd all by itself turned out to be faster than either reverse proxy plus Lighttpd.   I was benchmarking with ab, not sure if that made any difference.

I wasn't expecting lighttpd by itself to be faster though.</description>
		<content:encoded><![CDATA[<p>The odd thing when I benchmarked Lighttpd, Lighttpd + Squid, and Lighttpd + Varnish, Lighttpd all by itself turned out to be faster than either reverse proxy plus Lighttpd.   I was benchmarking with ab, not sure if that made any difference.</p>
<p>I wasn&#8217;t expecting lighttpd by itself to be faster though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Benchmark Caching of Varnish and Squid Again by Cherife Li</title>
		<link>http://dotimes.com/iscale/2008/04/benchmark-caching-of-varnish-and-squid-again.html#comment-68</link>
		<dc:creator>Cherife Li</dc:creator>
		<pubDate>Sat, 05 Apr 2008 01:37:07 +0000</pubDate>
		<guid isPermaLink="false">http://dotimes.com/iscale/?p=40#comment-68</guid>
		<description>[Comment ID #67 Will Be Quoted Here]
Yeah, this time the result is much better :-)
We now have one project run varnish, I think it's a better choice.
IMHO, there's no doubt that varnish is more powerful by reading its &lt;a href="http://varnish.projects.linpro.no/wiki/ArchitectNotes" target="_blank" rel="nofollow"&gt;architecture notes&lt;/a&gt;.
Thanks again for your time, Willy.</description>
		<content:encoded><![CDATA[<blockquote class='comment_quote'><p><a href="http://dotimes.com/iscale/2008/04/benchmark-caching-of-varnish-and-squid-again.html#comment-67" title="Click here to view the original comment"><em>willy tarreau on Sat, 05 Apr 2008 at 03:46 said:</em></a></p>
<p>Nice update! This benchmark is quite better now. As you see in vmstat, with varnish, only system CPU is used and there is a lot of idle time remaining. That means that varnish is optimized to induce a very low overhead. On the other side, you see both squid versions. They use half user and half system time, and the CPU is saturated (50% idle on a dual proc means 1 proc saturated). So squid is limited here by its architecture and design. If it consumed less user time, this time would be better spent in system which would simply double the<br />
performance, leading to approximately what you see in varnish. Maybe there are things that can be done with squid to optimize it, honnestly I don&#8217;t know. 25% user seems a lot to me on such a component, but since it&#8217;s a very flexible proxy I don&#8217;t know if there is an entry cost even if everything is disabled.</p>
<p>I think I will soon have to take a look at varnish, it looks promising :-)</p>
<p>Willy</p></blockquote>
<p>Yeah, this time the result is much better :-)<br />
We now have one project run varnish, I think it&#8217;s a better choice.<br />
IMHO, there&#8217;s no doubt that varnish is more powerful by reading its <a href="http://varnish.projects.linpro.no/wiki/ArchitectNotes" target="_blank" rel="nofollow" onclick="javascript:pageTracker._trackPageview ('/outbound/varnish.projects.linpro.no');">architecture notes</a>.<br />
Thanks again for your time, Willy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Benchmark Caching of Varnish and Squid Again by willy tarreau</title>
		<link>http://dotimes.com/iscale/2008/04/benchmark-caching-of-varnish-and-squid-again.html#comment-67</link>
		<dc:creator>willy tarreau</dc:creator>
		<pubDate>Fri, 04 Apr 2008 19:46:32 +0000</pubDate>
		<guid isPermaLink="false">http://dotimes.com/iscale/?p=40#comment-67</guid>
		<description>Nice update! This benchmark is quite better now. As you see in vmstat, with varnish, only system CPU is used and there is a lot of idle time remaining. That means that varnish is optimized to induce a very low overhead. On the other side, you see both squid versions. They use half user and half system time, and the CPU is saturated (50% idle on a dual proc means 1 proc saturated). So squid is limited here by its architecture and design. If it consumed less user time, this time would be better spent in system which would simply double the
performance, leading to approximately what you see in varnish. Maybe there are things that can be done with squid to optimize it, honnestly I don't know. 25% user seems a lot to me on such a component, but since it's a very flexible proxy I don't know if there is an entry cost even if everything is disabled.

I think I will soon have to take a look at varnish, it looks promising :-)

Willy</description>
		<content:encoded><![CDATA[<p>Nice update! This benchmark is quite better now. As you see in vmstat, with varnish, only system CPU is used and there is a lot of idle time remaining. That means that varnish is optimized to induce a very low overhead. On the other side, you see both squid versions. They use half user and half system time, and the CPU is saturated (50% idle on a dual proc means 1 proc saturated). So squid is limited here by its architecture and design. If it consumed less user time, this time would be better spent in system which would simply double the<br />
performance, leading to approximately what you see in varnish. Maybe there are things that can be done with squid to optimize it, honnestly I don&#8217;t know. 25% user seems a lot to me on such a component, but since it&#8217;s a very flexible proxy I don&#8217;t know if there is an entry cost even if everything is disabled.</p>
<p>I think I will soon have to take a look at varnish, it looks promising :-)</p>
<p>Willy</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Benchmark Caching of Varnish and Squid by IScale</title>
		<link>http://dotimes.com/iscale/2008/03/benchmark-caching-of-varnish-and-squid.html#comment-57</link>
		<dc:creator>IScale</dc:creator>
		<pubDate>Tue, 01 Apr 2008 08:06:37 +0000</pubDate>
		<guid isPermaLink="false">http://dotimes.com/iscale/2008/03/benchmark-caching-of-varnish-and-squid.html#comment-57</guid>
		<description>&lt;strong&gt;Benchmark Caching of Varnish and Squid Again...&lt;/strong&gt;

About two weeks ago, I did a simple benchmark on varnish and squid, and wrote this Benchmark Caching of Varnish and Squid post.
Today Willy Tarreau gave me some advise. So I took a short time re-ran this benchmark. Here follows the detail.
platform
Eve...</description>
		<content:encoded><![CDATA[<p><strong>Benchmark Caching of Varnish and Squid Again&#8230;</strong></p>
<p>About two weeks ago, I did a simple benchmark on varnish and squid, and wrote this Benchmark Caching of Varnish and Squid post.<br />
Today Willy Tarreau gave me some advise. So I took a short time re-ran this benchmark. Here follows the detail.<br />
platform<br />
Eve&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Benchmark Caching of Varnish and Squid by Cherife Li</title>
		<link>http://dotimes.com/iscale/2008/03/benchmark-caching-of-varnish-and-squid.html#comment-56</link>
		<dc:creator>Cherife Li</dc:creator>
		<pubDate>Tue, 01 Apr 2008 01:31:36 +0000</pubDate>
		<guid isPermaLink="false">http://dotimes.com/iscale/2008/03/benchmark-caching-of-varnish-and-squid.html#comment-56</guid>
		<description>[Comment ID #55 Will Be Quoted Here]
Yeah, you're right, that's a point. The ethernet controller of the proxy server is a bottleneck.
I'm not satisfied with this benchmark result. I'll re-run when I've got time.
Thanks for your advise, and your great HAProxy. :-)</description>
		<content:encoded><![CDATA[<blockquote class='comment_quote'><p><a href="http://dotimes.com/iscale/2008/03/benchmark-caching-of-varnish-and-squid.html#comment-55" title="Click here to view the original comment"><em>Willy Tarreau on Tue, 01 Apr 2008 at 05:16 said:</em></a></p>
<p>Hey, you have saturated your 100 Mbps network, your files were too<br />
big. You should retry either with Gigabit NICs, or with smaller files (far<br />
below 10 kB) to see how each proxy performs. I suspect that they did<br />
not eat much CPU either during the test.</p>
<p>Willy</p></blockquote>
<p>Yeah, you&#8217;re right, that&#8217;s a point. The ethernet controller of the proxy server is a bottleneck.<br />
I&#8217;m not satisfied with this benchmark result. I&#8217;ll re-run when I&#8217;ve got time.<br />
Thanks for your advise, and your great HAProxy. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Benchmark Caching of Varnish and Squid by Willy Tarreau</title>
		<link>http://dotimes.com/iscale/2008/03/benchmark-caching-of-varnish-and-squid.html#comment-55</link>
		<dc:creator>Willy Tarreau</dc:creator>
		<pubDate>Mon, 31 Mar 2008 21:16:56 +0000</pubDate>
		<guid isPermaLink="false">http://dotimes.com/iscale/2008/03/benchmark-caching-of-varnish-and-squid.html#comment-55</guid>
		<description>Hey, you have saturated your 100 Mbps network, your files were too
big. You should retry either with Gigabit NICs, or with smaller files (far
below 10 kB) to see how each proxy performs. I suspect that they did
not eat much CPU either during the test.

Willy</description>
		<content:encoded><![CDATA[<p>Hey, you have saturated your 100 Mbps network, your files were too<br />
big. You should retry either with Gigabit NICs, or with smaller files (far<br />
below 10 kB) to see how each proxy performs. I suspect that they did<br />
not eat much CPU either during the test.</p>
<p>Willy</p>
]]></content:encoded>
	</item>
</channel>
</rss>
