<?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>Mon, 20 May 2013 20:05:49 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Slawek Lukasiewicz's Blog: PHP application diagnostics - Memtrack]]></title>
      <guid>http://www.phpdeveloper.org/news/17102</guid>
      <link>http://www.phpdeveloper.org/news/17102</link>
      <description><![CDATA[<p>
<i>Slawek Lukasiewicz</i> has <a href="http://www.leftjoin.net/2011/11/php-application-diagnostics-memtrack/">posted about a handy tool</a> that can be used to track memory consumption and performance in your PHP application - <a href="http://php.net/manual/en/book.memtrack.php">memtrack</a>.
</p>
<blockquote>
Application profiling can help us determine bottlenecks and possible problems during development. But sometimes we also need to diagnose problems in production environment. Frequent performance problems are connected with functions and methods using too much memory.
</blockquote>
<p>
The tool allows you to set up thresholds for memory consumption and, if the scripts exceeds it, add warnings to your log files. He includes the simple instructions to install it (via <a href="http://pecl.php.net">PECL</a>) and enable it in your php.ini. Some sample code to create a memory overvload is included to test it out. <a href="http://www.php.net/manual/en/memtrack.ini.php">Configuration options</a> let you set the limits and define functions to ignore if you know for sure there's trouble spots.
</p>]]></description>
      <pubDate>Tue, 08 Nov 2011 12:08:37 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Antony Dovgal's Blog: locating memory hungry code with memtrack]]></title>
      <guid>http://www.phpdeveloper.org/news/11832</guid>
      <link>http://www.phpdeveloper.org/news/11832</link>
      <description><![CDATA[<p>
Sometimes finding that one spot in your code that's geting bloated and consuming at majority of your memory can be a bit difficult. <i>Antony Dovgal</i> has <a href="http://daylessday.org/archives/28-locating-memory-hungry-code-with-memtrack.html">proposed one solution</a> in a new post to his blog - the <a href="http://pecl.php.net/memtrack">memtrack extension</a> for from PECL.
</p>
<blockquote>
We needed to locate where most of the memory is allocated in our scripts (as some of them became too memory hungry), so I've created <a href="http://pecl.php.net/memtrack">memtrack</a> extension. This extension helps us to see unusually big memory allocations in production code.
</blockquote>
<p>
The extension logs memory usage information out to the standard error log file (however that'd defined on your system) and comes with a few configuration options. These let you control things like a "soft limit" at which to report the usage problems, the ability to ignore certain functions that you might know will cause a high load and and "vm_limit" setting that can help if your script is leaking memory at the end of its run.
</p>]]></description>
      <pubDate>Wed, 28 Jan 2009 11:19:18 -0600</pubDate>
    </item>
  </channel>
</rss>
