<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Hacking the Core of the Zend Framework</title>
	<atom:link href="http://blog.fedecarg.com/2008/07/14/hacking-the-core-of-the-zend-framework/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.fedecarg.com/2008/07/14/hacking-the-core-of-the-zend-framework/</link>
	<description>Simple is better than complex. Complex is better than complicated. &#124; @fedecarg</description>
	<lastBuildDate>Mon, 06 Feb 2012 14:38:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: federico</title>
		<link>http://blog.fedecarg.com/2008/07/14/hacking-the-core-of-the-zend-framework/#comment-881</link>
		<dc:creator><![CDATA[federico]]></dc:creator>
		<pubDate>Tue, 15 Jul 2008 00:20:23 +0000</pubDate>
		<guid isPermaLink="false">http://phpimpact.wordpress.com/?p=300#comment-881</guid>
		<description><![CDATA[I agree, it&#039;s confusing. I&#039;ve updated the post:

&quot;Measuring the performance of an application (at design time) when placed under ever increasing loads helps improve the scalability of that application.&quot; 

Thanks]]></description>
		<content:encoded><![CDATA[<p>I agree, it&#8217;s confusing. I&#8217;ve updated the post:</p>
<p>&#8220;Measuring the performance of an application (at design time) when placed under ever increasing loads helps improve the scalability of that application.&#8221; </p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: khelonium</title>
		<link>http://blog.fedecarg.com/2008/07/14/hacking-the-core-of-the-zend-framework/#comment-878</link>
		<dc:creator><![CDATA[khelonium]]></dc:creator>
		<pubDate>Mon, 14 Jul 2008 23:05:59 +0000</pubDate>
		<guid isPermaLink="false">http://phpimpact.wordpress.com/?p=300#comment-878</guid>
		<description><![CDATA[Improving performance means that your code is vertically scalable and in the same time it  is also vertically scalable because you can add more hardware or you can tweak you system. Of course the design can affect the scalability , but again , performance is not the same thing as scalability , it is just a variable used to compute scalability. 

Measuring scalability is saying how  much you can  improve before you tweak. Scalability is also used to approximate the max you can get, either horizontally or vertically , trough software or hardware before reaching that max. At least this is what i understand.

Measuring performance is not the same thing as measuring scalability. I think :

&quot;measuring the performance of an application when placed under ever increasing loads determines the scalability of that application.&quot; is partially wrong.

I hope that this answer makes sense.]]></description>
		<content:encoded><![CDATA[<p>Improving performance means that your code is vertically scalable and in the same time it  is also vertically scalable because you can add more hardware or you can tweak you system. Of course the design can affect the scalability , but again , performance is not the same thing as scalability , it is just a variable used to compute scalability. </p>
<p>Measuring scalability is saying how  much you can  improve before you tweak. Scalability is also used to approximate the max you can get, either horizontally or vertically , trough software or hardware before reaching that max. At least this is what i understand.</p>
<p>Measuring performance is not the same thing as measuring scalability. I think :</p>
<p>&#8220;measuring the performance of an application when placed under ever increasing loads determines the scalability of that application.&#8221; is partially wrong.</p>
<p>I hope that this answer makes sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: federico</title>
		<link>http://blog.fedecarg.com/2008/07/14/hacking-the-core-of-the-zend-framework/#comment-874</link>
		<dc:creator><![CDATA[federico]]></dc:creator>
		<pubDate>Mon, 14 Jul 2008 15:35:45 +0000</pubDate>
		<guid isPermaLink="false">http://phpimpact.wordpress.com/?p=300#comment-874</guid>
		<description><![CDATA[That&#039;s right, the responsibility for application performance occurs both at design time and at run time. You are talking about run time, I&#039;m talking about design time. From an design point of view, when performance begins to fall below the stated minimum performance requirements, it means that you have reached the limit of the application&#039;s scalability, and therefore it will perform poorly. Of course, there are many ways to scale poorly designed applications at run time, for example, scaling up (using better, faster, and more expensive hardware).

&lt;blockquote&gt;Answering performance related problems has little to do with scalability even if sometimes it can be a key factor.&lt;/blockquote&gt;

Well, like I said before, you are talking about performance at a higher level (hardware), I&#039;m talking about performance at a lower level (application design). ]]></description>
		<content:encoded><![CDATA[<p>That&#8217;s right, the responsibility for application performance occurs both at design time and at run time. You are talking about run time, I&#8217;m talking about design time. From an design point of view, when performance begins to fall below the stated minimum performance requirements, it means that you have reached the limit of the application&#8217;s scalability, and therefore it will perform poorly. Of course, there are many ways to scale poorly designed applications at run time, for example, scaling up (using better, faster, and more expensive hardware).</p>
<blockquote><p>Answering performance related problems has little to do with scalability even if sometimes it can be a key factor.</p></blockquote>
<p>Well, like I said before, you are talking about performance at a higher level (hardware), I&#8217;m talking about performance at a lower level (application design).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: khelonium</title>
		<link>http://blog.fedecarg.com/2008/07/14/hacking-the-core-of-the-zend-framework/#comment-872</link>
		<dc:creator><![CDATA[khelonium]]></dc:creator>
		<pubDate>Mon, 14 Jul 2008 15:23:04 +0000</pubDate>
		<guid isPermaLink="false">http://phpimpact.wordpress.com/?p=300#comment-872</guid>
		<description><![CDATA[&quot;I’ve been testing mostly the performance of the framework, as I believe that measuring the performance of an application when placed under ever increasing loads determines the scalability of that application.&quot;

Performance is not the same thing as scalability.I trust that you know this, but there are many people who tune for speed and then argue about scalability by reading many scalability related posts in which performance is always mentioned.

If you are testing only the Front Controller you can increase the load as much as you like , by adding more servers it will always scale up to a point , so it&#039;s scalable. Same goes for vertical scaling by adding new hardware. Whether it&#039;s 1 r/s or 1000 r/s , it does not matter , it is still scalable.  

Answering performance related problems has little  to do with scalability even if sometimes it can be a key factor. 

(and zend controller front is cool yes).]]></description>
		<content:encoded><![CDATA[<p>&#8220;I’ve been testing mostly the performance of the framework, as I believe that measuring the performance of an application when placed under ever increasing loads determines the scalability of that application.&#8221;</p>
<p>Performance is not the same thing as scalability.I trust that you know this, but there are many people who tune for speed and then argue about scalability by reading many scalability related posts in which performance is always mentioned.</p>
<p>If you are testing only the Front Controller you can increase the load as much as you like , by adding more servers it will always scale up to a point , so it&#8217;s scalable. Same goes for vertical scaling by adding new hardware. Whether it&#8217;s 1 r/s or 1000 r/s , it does not matter , it is still scalable.  </p>
<p>Answering performance related problems has little  to do with scalability even if sometimes it can be a key factor. </p>
<p>(and zend controller front is cool yes).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

