<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="http://www.illusori.co.uk/xsl/rss.xsl" media="screen"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Sam's Blog &gt; Analysis</title>
    <link>http://www.illusori.co.uk/blog/categories/analysis/</link>
    <description>Sam's Blog, feed for category analysis</description>
    <language>en-gb</language>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <pubDate>Sat, 27 Mar 2010 20:28:00 GMT</pubDate>
    <lastBuildDate>Sat, 27 Mar 2010 20:28:00 GMT</lastBuildDate>
    <generator>build_site 1.0</generator>
    <webMaster>rss@illusori.co.uk</webMaster>

    <item>
      <title><![CDATA[Wrapping Benchmark.pm to auto-correct custom controls]]></title>
      <link>http://www.illusori.co.uk/blog/2010/03/27/wrapping_for_better_benchmarking.html</link>
      <description><![CDATA[<p>Last week, in <a href="/blog/2010/03/18/monkey_patching_for_better_benchmarks.html">&quot;Monkey-patching Benchmark.pm to auto-correct custom controls&quot;</a>,
we covered how to monkey-patch <a href="http://search.cpan.org/perldoc?Benchmark">Benchmark.pm</a> into giving
us the results we wanted, and saw that one alternative method was to
wrap the module instead.</p>
<p>This week, we investigate how to do this, and see what unpleasant surprises
lie in wait when wrapping a procedural module.</p><p><a href="http://www.illusori.co.uk/blog/2010/03/27/wrapping_for_better_benchmarking.html">Read more...</a></p>]]></description>
      <dc:creator>Sam Graham</dc:creator>
      <category>perl</category>
      <category>ironman</category>
      <category>benchmarking</category>
      <category>analysis</category>
      <category>module-wrapping</category>
      <category>tutorial</category>
      <category>basic</category>
      <pubDate>Sat, 27 Mar 2010 20:28:00 GMT</pubDate>
      <guid isPermaLink="true">http://www.illusori.co.uk/blog/2010/03/27/wrapping_for_better_benchmarking.html</guid>
    </item>
    <item>
      <title><![CDATA[Monkey-patching Benchmark.pm to auto-correct custom controls]]></title>
      <link>http://www.illusori.co.uk/blog/2010/03/18/monkey_patching_for_better_benchmarks.html</link>
      <description><![CDATA[<p>In <a href="/blog/2010/03/05/advanced_benchmark_analysis_1.html">&quot;Advanced Benchmark Analysis I: Yet more white-space trimming&quot;</a>,
I mentioned that you could automatically take into account the
cost of your control benchmark and eliminate it from the rest
of your results.</p>
<p>This blog entry shows you how to monkey-patch <a href="http://search.cpan.org/perldoc?Benchmark">Benchmark.pm</a>
to let you do just that.</p><p><a href="http://www.illusori.co.uk/blog/2010/03/18/monkey_patching_for_better_benchmarks.html">Read more...</a></p>]]></description>
      <dc:creator>Sam Graham</dc:creator>
      <category>perl</category>
      <category>ironman</category>
      <category>benchmarking</category>
      <category>analysis</category>
      <category>monkey-patching</category>
      <category>hack</category>
      <category>tutorial</category>
      <category>advanced</category>
      <pubDate>Thu, 18 Mar 2010 13:41:00 GMT</pubDate>
      <guid isPermaLink="true">http://www.illusori.co.uk/blog/2010/03/18/monkey_patching_for_better_benchmarks.html</guid>
    </item>
    <item>
      <title><![CDATA[Advanced Benchmark Analysis II: Probing strengths and weaknesses]]></title>
      <link>http://www.illusori.co.uk/blog/2010/03/09/advanced_benchmark_analysis_2.html</link>
      <description><![CDATA[<p>In my previous blog entry,
<a href="/blog/2010/03/05/advanced_benchmark_analysis_1.html">&quot;Advanced Benchmark Analysis I: Yet more white-space trimming&quot;</a>,
I left you with the thought that our benchmarks changed
with changing input.</p>
<p>This article shows you how to analyze those changes
and how to draw conclusions from them.</p><p><a href="http://www.illusori.co.uk/blog/2010/03/09/advanced_benchmark_analysis_2.html">Read more...</a></p>]]></description>
      <dc:creator>Sam Graham</dc:creator>
      <category>perl</category>
      <category>ironman</category>
      <category>benchmarking</category>
      <category>analysis</category>
      <category>trim</category>
      <category>regexp</category>
      <category>optimization</category>
      <category>advanced</category>
      <category>tutorial</category>
      <pubDate>Tue, 09 Mar 2010 13:39:00 GMT</pubDate>
      <guid isPermaLink="true">http://www.illusori.co.uk/blog/2010/03/09/advanced_benchmark_analysis_2.html</guid>
    </item>
    <item>
      <title><![CDATA[Advanced Benchmark Analysis I: Yet more white-space trimming]]></title>
      <link>http://www.illusori.co.uk/blog/2010/03/05/advanced_benchmark_analysis_1.html</link>
      <description><![CDATA[<p>Seems my previous blog, <a href="/blog/2010/03/03/white_space_trim.html">&quot;Some
simple &quot;white-space trim&quot; benchmarks&quot;</a> caught people&#39;s attention,
and I&#39;ve received some interesting suggestions and observations worthy
of a followup article, this also gives me the chance to delve into
explaining more advanced benchmark analysis.</p>
<p>So, <i>deep breath</i>, here goes.</p><p><a href="http://www.illusori.co.uk/blog/2010/03/05/advanced_benchmark_analysis_1.html">Read more...</a></p>]]></description>
      <dc:creator>Sam Graham</dc:creator>
      <category>perl</category>
      <category>ironman</category>
      <category>benchmarking</category>
      <category>analysis</category>
      <category>trim</category>
      <category>regexp</category>
      <category>optimization</category>
      <category>intermediate</category>
      <category>tutorial</category>
      <pubDate>Fri, 05 Mar 2010 09:43:00 GMT</pubDate>
      <guid isPermaLink="true">http://www.illusori.co.uk/blog/2010/03/05/advanced_benchmark_analysis_1.html</guid>
    </item>

  </channel>
</rss>
