<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 19 Jun 2013 05:39:48 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Kenny Katzgrau's Blog: Enable Site-Wide Profiling With CodeIgniter]]></title>
      <guid>http://www.phpdeveloper.org/news/15656</guid>
      <link>http://www.phpdeveloper.org/news/15656</link>
      <description><![CDATA[<p>
On his blog today <i>Kenny Katzgrau</i> talks about a handy feature of the <a href="http://codeigniter.com">CodeIgniter</a> framework - profiling - and how you can <a href="http://codefury.net/2009/11/enable-site-wide-profiling-with-codeigniter/">implement it site-wide</a> rather than just on a controller by controller basis.
</p>
<blockquote>
In your controller before you load a view, CodeIgniter will give you information regarding how fast the page loaded, how many SQL queries executed, the content of each query, and the running time of each query. This is incredibly useful when you are trying to debug your application, or simply see how quickly things are loading. There's only one problem: To enable profiling, that line of code above must be present. What if you want to profile several pages, or even your whole web application?
</blockquote>
<p>
He turned to another built-in feature of the framework, the controller hooks it allows, to set up a simple post-controller execution that gets a new CodeIgniter instance and enables the profiling configuration item. This is a much better option than having to put the line in each and every controller and method he might want profiled.
</p>]]></description>
      <pubDate>Thu, 30 Dec 2010 09:07:33 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[ThinkPHP Blog: Benchmarking & optimizing real-world scenarios in a business context]]></title>
      <guid>http://www.phpdeveloper.org/news/14671</guid>
      <link>http://www.phpdeveloper.org/news/14671</link>
      <description><![CDATA[<p>
On the ThinkPHP blog today there's <a href="http://blog.mayflower.de/archives/550-Profiling-best-practices-Benchmarking-and-optimizing-real-world-scenarios-in-a-business-context.html#extended">a new article</a> looking at some of the best practices they seen when it comes to profiling and benchmarking your PHP-based applications.
</p>
<blockquote>
Over the years, PHP has evolved from a script language to a programming language used in big applications with high-level architectures. As the most popular language for web applications, PHP is very fast, robust and stable by default. Coming from tiny scripts, PHP is used in large-scale web applications nowadays. In terms of business context, we need to focus on these three key factors: Scalability, Responsiveness and Resource misusage. All three factors have a high impact on hardware costs, customer loyalty and - indirectly - sales.
</blockquote>
<p>
They mention a few ways that you can use to optimize your application's code including evaluating resource limitations, Firebug caching results and finding bottlenecks with something like <a href="http://github.com/mayflowergmbh/xdebug">XDebug</a>.
</p>]]></description>
      <pubDate>Fri, 18 Jun 2010 09:14:35 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[ProPHP Podcast: Newscast for Dec 12th, 2007]]></title>
      <guid>http://www.phpdeveloper.org/news/9308</guid>
      <link>http://www.phpdeveloper.org/news/9308</link>
      <description><![CDATA[<p>
The Pro::PHP Podcast has released their <a href="http://podcast.phparch.com/main/index.php/episodes:20071220">latest episode</a> - the Newscast for December 20th, 2007.
</p>
<p>
Topics mentioned include:
</p>
<ul>
<li><a href="http://blog.calevans.com/2007/12/19/a-little-php-fun-while-you-are-winding-down-for-the-holidays/">PHPCity</a>
<li>Thoughts on <a href="http://mtabini.blogspot.com/2007/12/thoughts-for-new-year-php-as-new-java.html">PHP as the next Java</a>
<li>The <a href="http://code.google.com/apis/chart/">Google Charting API</a>
<li><a href="http://blogs.reucon.com/srt/2007/12/13/profiling_php_applications.html">Profiling PHP applications</a>
</ul>
<p>
To grab this latest show you can either <a href="http://podcast.phparch.com/podcast/rss/index.xml">subscribe to their feed</a> or you can just <a href="http://podcast.phparch.com/podcast/audio/20071220.mp3">get the latest show</a> via a direct mp3 download.
</p>]]></description>
      <pubDate>Tue, 25 Dec 2007 08:13:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Gergely Hodicska's Blog: What is new in PHP 5.3 - Part 4]]></title>
      <guid>http://www.phpdeveloper.org/news/9078</guid>
      <link>http://www.phpdeveloper.org/news/9078</link>
      <description><![CDATA[<p>
<i>Gergely Hodicska</i> has posted <a href="http://blog.felho.hu/what-is-new-in-php-53-part-4-__callstatic-openid-support-userini-xslt-profiling-and-more.html">part four</a> of his "what's new in PHP 5.3" series - a sort of "wrapup" for some of the smaller features that have been added. Among them are:
</p>
<ul>
<li>__callStatic
<li>OpenID support
<li>user.ini user defined ini functionality
<li>dynamic static calls
<li>XSLT profiling
</ul>
<p>
...and many more. Check out <a href="http://blog.felho.hu/what-is-new-in-php-53-part-4-__callstatic-openid-support-userini-xslt-profiling-and-more.html">the post</a> for more to add to the list and for some brief examples of the ones already mentioned.
</p>]]></description>
      <pubDate>Tue, 20 Nov 2007 09:38:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Christian Stocker's Blog: Added xslt profiling to PHP 5.3 and 6 CVS]]></title>
      <guid>http://www.phpdeveloper.org/news/8762</guid>
      <link>http://www.phpdeveloper.org/news/8762</link>
      <description><![CDATA[<p>
<i>Christian Stocker</i> <a href="http://blog.liip.ch/archive/2007/10/02/added-xslt-profiling-to-php-5-3-and-6-cvs.html">briefly mentions</a> a new addition he's made to the post-PHP5.3 branching of the main trunk of the PHP development - XSLT profiling.
</p>
<blockquote>
After PHP 5.3 was branched (for making place for - among other new stuff - namespaces), it was finally time to put my <a href="http://blog.liip.ch/archive/2007/04/29/profile-xslt-transformations-within-php.html">XSLT profiling addition</a> into the official PHP sources.
</blockquote>
<p>
The <a href="http://blog.liip.ch/archive/2007/04/29/profile-xslt-transformations-within-php.html">addition</a> allows you to check in on your XSLT translations and see which spots in it are taking the most time to parse. This can be a very valuable tool when trying to see into the "black box" that PHP has around XSLT transformations. PHP 5.2ers can get the same functionality with <a href="https://svn.liip.ch/repos/public/misc/xslpatches/xslt-profiling-php.patch">this patch</a> too.
</p>]]></description>
      <pubDate>Tue, 02 Oct 2007 08:45:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[php|architect: August 2007 Issue Released]]></title>
      <guid>http://www.phpdeveloper.org/news/8478</guid>
      <link>http://www.phpdeveloper.org/news/8478</link>
      <description><![CDATA[<p>
<a href="http://phparch.com">php|architect</a> magazine has released their latest issue - the <a href="http://www.phparch.com/issue.php?mid=110">August 2007</a> edition. The cover story for this month is a piece by <i>Dirk Merkel</i> covering the automation and benchmarking/code profiling of your application to find potential issues before your customers/users do.
</p>
<p>
Other great articles in this issue include:
</p>
<ul>
<li>a look at Flex and the Zend Framework
<li>part one of a series on normalization (Chinese)
<li>using cURL to extract pages and their data
<li>"The Job Interview" - an insiders guide.
</ul>
<p>
There's two ways to get this issue - you can either <a href="http://www.phparch.com/publication.php?pid=1">subscribe to the magazine</a> for a year (the PDF edition is only $40 USD) or you can buy the <a href="http://www.phparch.com/issue.php?mid=110">single issue</a> for about $5 USD.
</p>]]></description>
      <pubDate>Fri, 17 Aug 2007 09:32:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[SitePoint PHP Blog: PHP Frontend for Xdebug Profiling?]]></title>
      <guid>http://www.phpdeveloper.org/news/5228</guid>
      <link>http://www.phpdeveloper.org/news/5228</link>
      <description><![CDATA[<p>
On the SitePoint PHP Blog, <i>Harry Fuecks</i> has posted <a href="http://www.sitepoint.com/blogs/2006/04/20/php-frontend-for-xdebug-profiling/">an interesting bit</a> asking about a PHP frontend for Xdebug profiling, specifically for the 2.x version's output.
</p>
<quote>
<i>
Xdebug 1.x had this nice xdebug_dump_function_profile() function which planted a HTML table containing the profiling stats in your output'"nice an easy to use, ignoring the minor issue that doing this "in band" with the code you are profiling slants the results. With Xdebug 2.x it was dropped and you now need a tool like <a href="http://kcachegrind.sourceforge.net/">kcachegrind</a> or <a href="http://sourceforge.net/projects/wincachegrind/">wincachegrind</a>, an output file generated by Xdebug acting as the middle man.
</i>
</quote>
<p>
Several of <a href="http://www.sitepoint.com/blogs/2006/04/20/php-frontend-for-xdebug-profiling/#comments">the comments</a> either ask why he would want to write it when the two tools he mentions work just fine or a few links to scripts out there that already do this sort of thing. If you've been looking for something like this, definitely check out this post - there's a few resources in there you don't want to miss.
</p>]]></description>
      <pubDate>Mon, 24 Apr 2006 07:34:09 -0500</pubDate>
    </item>
  </channel>
</rss>
