<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Inkzee &#187; webserver</title>
	<atom:link href="http://blog.inkzee.com/index.php/tag/webserver/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.inkzee.com</link>
	<description>How to read more in less time</description>
	<lastBuildDate>Wed, 12 May 2010 13:23:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/>		<item>
		<title>Cherokee Web Server&#8230; when lighter and faster is a must</title>
		<link>http://blog.inkzee.com/index.php/2010/05/12/cherokee-web-server-when-lighter-and-faster-is-a-must/</link>
		<comments>http://blog.inkzee.com/index.php/2010/05/12/cherokee-web-server-when-lighter-and-faster-is-a-must/#comments</comments>
		<pubDate>Wed, 12 May 2010 13:23:28 +0000</pubDate>
		<dc:creator>luis</dc:creator>
				<category><![CDATA[inkzee]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[cherokee]]></category>
		<category><![CDATA[history]]></category>
		<category><![CDATA[lighthttpd]]></category>
		<category><![CDATA[webserver]]></category>

		<guid isPermaLink="false">http://blog.inkzee.com/?p=100</guid>
		<description><![CDATA[Sometimes when it comes to choosing a web server we always end up in the same decision: Apache&#8230; it&#8217;s alright, it&#8217;s the most widely used web server but that doesn&#8217;t mean it&#8217;s the best one. When we started with Inkzee we didn&#8217;t think too much about other alternatives&#8230; we started with Apache and it&#8217;s not [...]]]></description>
			<content:encoded><![CDATA[<p>Sometimes when it comes to <strong>choosing a web server</strong> we always end up in the same decision: <strong>Apache</strong>&#8230; it&#8217;s alright, it&#8217;s the most widely used web server but that <strong>doesn&#8217;t mean it&#8217;s the best one</strong>.</p>
<p><img class="alignright size-medium wp-image-103" style="margin: 5px;" title="cherokee2-mini" src="http://blog.inkzee.com/wp-content/uploads/cherokee2-mini-300x116.png" alt="" width="300" height="116" /></p>
<p>When we started with Inkzee we didn&#8217;t think too much about <strong>other alternatives</strong>&#8230; we started with Apache and it&#8217;s not that we had big complaints about it, but having all the backend in one machine made us have<strong> performance/low resource consumption requirements</strong> and after a few months of our service running the all the different backend subsystems were almost killing the server and we started to research alternatives.</p>
<p>We were going to change Apache for Lighttpd but then we stepped into<strong> </strong><a href="http://www.cherokee-project.com/"><strong>Cherokee</strong></a> <a href="http://www.cherokee-project.com/benchmarks.html">statistics</a> and after reading some reviews we decided to give it a try, the numbers spoke for themselves. We had been checking on Che</p>
<p>rokee for some years now, the project was mature enough for our needs so we went for it.</p>
<p>After a year and a half we can write our own<strong> lessons-learned</strong> from our experience:</p>
<ul>
<li>The <strong><a href="http://www.cherokee-project.com/cgi-bin/mailman/listinfo/cherokee">Cherokee team</a></strong> have been so <strong>responsive</strong> to every problem or tweak we wanted to do with our server.</li>
<li>The <a href="http://www.cherokee-project.com/doc/bundle_cherokee-admin.html">admin interface </a>is pretty rad, if you are not used to messing with config files you&#8217;ll find no challenge.</li>
<li>We didn&#8217;t miss anything: <strong>FastCGI</strong>, <strong>PHP</strong>, TLS and SSL, Load Balancer, Reverse Proxy, statics cache, &#8230;</li>
<li>And the most important for us: our servers stand the load so much better now&#8230; indeed now we are still able to have our service in <strong>just one server</strong> <img src='http://blog.inkzee.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </li>
</ul>
<p>So, dare to try it now that Cherokee is celebrating their <strong><a href="http://summit.cherokee-project.com/">version 1.0 release</a></strong>, it&#8217;s a really nice product worth trying.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.inkzee.com/index.php/2010/05/12/cherokee-web-server-when-lighter-and-faster-is-a-must/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Better performance</title>
		<link>http://blog.inkzee.com/index.php/2008/08/02/better-performance/</link>
		<comments>http://blog.inkzee.com/index.php/2008/08/02/better-performance/#comments</comments>
		<pubDate>Sat, 02 Aug 2008 00:13:03 +0000</pubDate>
		<dc:creator>abarrera</dc:creator>
				<category><![CDATA[inkzee]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[cherokee]]></category>
		<category><![CDATA[memcache]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[response]]></category>
		<category><![CDATA[webserver]]></category>

		<guid isPermaLink="false">http://blog.inkzee.com/?p=16</guid>
		<description><![CDATA[Because for us, speed is one of our primary targets, we&#8217;ve just pushed a new update to our backend that enables memcache support for some parts of our code. It&#8217;s not all there yet, but the basics are there and response times will start getting better. Right now, you&#8217;ll be able to experience a much [...]]]></description>
			<content:encoded><![CDATA[<p>Because for us, speed is one of our primary targets, we&#8217;ve just pushed a <strong>new update</strong> to our backend that enables <strong>memcache</strong> <strong>support</strong> for some parts of our code. It&#8217;s not all there yet, but the <strong>basics</strong> are there and response times will start getting better.</p>
<p>Right now, you&#8217;ll be able to experience a <strong>much better performance</strong> when reading posts and fetching a list of titles from a given feed. During the next days we hope the response time will get better and better.</p>
<p>We&#8217;ve also <strong>migrated our webservers</strong> today from <strong>Apache</strong> to <strong>Cherokee</strong>. Although Apache is excellent in many ways, we don&#8217;t need a fully loaded Apache, so we&#8217;ve chosen Cherokee which is working fine for us.</p>
<p><strong>Thanks a lot for your patient</strong>!! And please, do sends us an email with any feedback you&#8217;ve got!</p>
<p>Have a nice weekend all!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.inkzee.com/index.php/2008/08/02/better-performance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

