<story><title>Refactored PHP engine makes Wordpress 20% faster</title><url>http://news.php.net/php.internals/73888</url></story><parent_chain><item><author>lucb1e</author><text>&amp;gt; Wordpress 3.6 – 20.0% gain (253 vs 211 req&amp;#x2F;sec)&lt;p&gt;How do you generate 211 pages per second on Wordpress to begin with? My server does page generation for my own custom-built blog in ~15ms, but takes a whopping three seconds for a single Wordpress page. I know it&amp;#x27;s somewhat offtopic and it&amp;#x27;s about the relative results, but what hardware is this?</text></item></parent_chain><comment><author>dangrossman</author><text>My Linode VPS spits out WordPress pages in 33.811ms (via ApacheBench, concurrency=10 for a couple hundred requests). I don&amp;#x27;t use any kind of content&amp;#x2F;page cache. There&amp;#x27;s no reason WordPress would be 200 times slower than your custom blog -- WordPress isn&amp;#x27;t some kind of complex software. It&amp;#x27;s a handful of very small PHP classes that choose a theme file based on the URL, include it, run a database query to select some posts, wrap the result rows in objects, and pass them to the theme to spit out. I&amp;#x27;ve had hundreds of concurrent visitors on my blog without registering any load. If your site is taking 3 seconds to return a page, there&amp;#x27;s something wrong and it&amp;#x27;s not the choice of blog platform.</text></comment>
<story><title>Refactored PHP engine makes Wordpress 20% faster</title><url>http://news.php.net/php.internals/73888</url></story><parent_chain><item><author>lucb1e</author><text>&amp;gt; Wordpress 3.6 – 20.0% gain (253 vs 211 req&amp;#x2F;sec)&lt;p&gt;How do you generate 211 pages per second on Wordpress to begin with? My server does page generation for my own custom-built blog in ~15ms, but takes a whopping three seconds for a single Wordpress page. I know it&amp;#x27;s somewhat offtopic and it&amp;#x27;s about the relative results, but what hardware is this?</text></item></parent_chain><comment><author>pjbrunet</author><text>Could just be your hosting.  For example, with Media Temple (years ago) I found it often took 7+ seconds just to redirect www to non-www, up to 12 seconds.  Pingdom is a good tool to see where you&amp;#x27;re getting stuck &lt;a href=&quot;http://tools.pingdom.com/fpt/&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;tools.pingdom.com&amp;#x2F;fpt&amp;#x2F;&lt;/a&gt; Another common problem, your MySQL database could be overloaded (especially with shared hosting) and more caching won&amp;#x27;t necessarily solve the problem.</text></comment>