<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Profiling on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/profiling/</link><description>Recent content in Profiling on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Wed, 27 Mar 2013 21:03:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/profiling/index.xml" rel="self" type="application/rss+xml"/><item><title>Run time profiling with cProfile</title><link>http://karpoke.ignaciocano.com/2013/03/27/run-time-profiling-with-cprofile/</link><pubDate>Wed, 27 Mar 2013 21:03:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2013/03/27/run-time-profiling-with-cprofile/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Python is distributed with profiling modules. They describe the run
time operation of a pure python program, providing a variety of
statistics.&lt;/p&gt;
&lt;p&gt;The cProfile module is the recommended module. To execute your program
under the control of the cProfile module, a simple form is:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;$ python -m cProfile -s cumulative mypythonscript.py
&lt;/code&gt;&lt;/pre&gt;
&lt;/blockquote&gt;
&lt;p&gt;» Alain Leufroy | &lt;a href="http://www.logilab.org/blogentry/104898"&gt;logilab.org&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>