<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Amund Tveit's Blog - Latest Comments in Tools for Accelerating Python</title><link>http://amund.disqus.com/</link><description></description><atom:link href="https://amund.disqus.com/tools_for_accelerating_python/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 17 Dec 2008 01:03:31 -0000</lastBuildDate><item><title>Re: Tools for Accelerating Python</title><link>http://amundblog.blogspot.com/2008/11/tools-for-accelerating-python.html#comment-4446313</link><description>&lt;p&gt;Great list, thankx&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jeremy</dc:creator><pubDate>Wed, 17 Dec 2008 01:03:31 -0000</pubDate></item><item><title>Re: Tools for Accelerating Python</title><link>http://amundblog.blogspot.com/2008/11/tools-for-accelerating-python.html#comment-4203389</link><description>&lt;p&gt;Excellent list. Can you post similar tools for Google App Engine too.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ashish</dc:creator><pubDate>Fri, 05 Dec 2008 09:31:00 -0000</pubDate></item><item><title>Re: Tools for Accelerating Python</title><link>http://amundblog.blogspot.com/2008/11/tools-for-accelerating-python.html#comment-4082154</link><description>&lt;p&gt;Putting Stackless Python and threads in the same breath seems pretty misleading to me, and I would think long and hard before using either approach.  Rewrite your code with threads, and you need to make sure at least one of your threads will be spending enough time in C code that releases the GIL to actually give the other thread time to run concurrently, or else you've just wasted a lot of time and introduced a whole lot of concurrency bugs to write a program that still only runs on one core most of the time, thanks to the aforementioned GIL.&lt;/p&gt;&lt;p&gt;Stackless Python gives you logical parallelism, but it doesn't really give you distribution.  You may have 100,000 tasklets running, but you're still only using one core of your one processor until you use one of the other approaches to actually parallelize your program.  Stackless will allow you to then pickle your tasklets and swap them between processes or machines, but you've just tossed a lot of the nice, deterministic nature of Stackless tasklets out the window.&lt;/p&gt;&lt;p&gt;It also bears mentioning that RPython isn't really specified and isn't intended for use outside of PyPy, meaning it might change out from underneath you if you try to build anything on top of it, and it apparently has some pretty awful error handling (are you alright with your Python program segfaulting?) I'd love for them to standardize it and be willing to make RPython a language for general use, but they aren't willing to do that yet.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ben Cummings</dc:creator><pubDate>Mon, 01 Dec 2008 08:53:03 -0000</pubDate></item><item><title>Re: Tools for Accelerating Python</title><link>http://amundblog.blogspot.com/2008/11/tools-for-accelerating-python.html#comment-4072634</link><description>&lt;p&gt;You should add the multiprocessing module as well. (PyProcessing before it was included in the standard library.)&lt;br&gt;When seeking to take advantage of multiple cores, it performs well enough.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">lorg</dc:creator><pubDate>Sun, 30 Nov 2008 12:15:26 -0000</pubDate></item><item><title>Re: Tools for Accelerating Python</title><link>http://amundblog.blogspot.com/2008/11/tools-for-accelerating-python.html#comment-4069686</link><description>&lt;p&gt;Thanks Ian, added a benchmark link next to ShedSkin&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">amund</dc:creator><pubDate>Sun, 30 Nov 2008 09:00:44 -0000</pubDate></item><item><title>Re: Tools for Accelerating Python</title><link>http://amundblog.blogspot.com/2008/11/tools-for-accelerating-python.html#comment-4069682</link><description>&lt;p&gt;Thanks Jacinto, added now.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">amund</dc:creator><pubDate>Sun, 30 Nov 2008 09:00:10 -0000</pubDate></item><item><title>Re: Tools for Accelerating Python</title><link>http://amundblog.blogspot.com/2008/11/tools-for-accelerating-python.html#comment-4069399</link><description>&lt;p&gt;I've recently written a long article on using ShedSkin to give my Python neural-network code a 196* speed increase.  Several contributors took the code and made Cython, Numpy and raw-C variants alongside my Vanilla Python and Psyco timings to offer their own comparisons.&lt;br&gt;The numbers are very useful if you're looking into these frameworks:&lt;br&gt;&lt;a href="http://ianozsvald.com/2008/11/17/making-python-math-196-faster-with-shedskin/" rel="nofollow noopener" target="_blank" title="http://ianozsvald.com/2008/11/17/making-python-math-196-faster-with-shedskin/"&gt;http://ianozsvald.com/2008/...&lt;/a&gt;&lt;br&gt;Ian.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Ozsvald</dc:creator><pubDate>Sun, 30 Nov 2008 07:58:28 -0000</pubDate></item><item><title>Re: Tools for Accelerating Python</title><link>http://amundblog.blogspot.com/2008/11/tools-for-accelerating-python.html#comment-4069361</link><description>&lt;p&gt;There is also Boost.Python which provides interoperability between Python and C++.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jacinto</dc:creator><pubDate>Sun, 30 Nov 2008 07:49:04 -0000</pubDate></item><item><title>Re: Tools for Accelerating Python</title><link>http://amundblog.blogspot.com/2008/11/tools-for-accelerating-python.html#comment-4068160</link><description>&lt;p&gt;thanks George, have added those now.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">amund</dc:creator><pubDate>Sun, 30 Nov 2008 04:32:24 -0000</pubDate></item><item><title>Re: Tools for Accelerating Python</title><link>http://amundblog.blogspot.com/2008/11/tools-for-accelerating-python.html#comment-4066507</link><description>&lt;p&gt;Hi. Maybe, you should also add Twisted and rpyc...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">George</dc:creator><pubDate>Sat, 29 Nov 2008 22:40:42 -0000</pubDate></item><item><title>Re: Tools for Accelerating Python</title><link>http://amundblog.blogspot.com/2008/11/tools-for-accelerating-python.html#comment-4064853</link><description>&lt;p&gt;Thanks, wasn't aware of Cython, will have a look. (The one I most recently tested was cinpy)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">amund</dc:creator><pubDate>Sat, 29 Nov 2008 18:07:02 -0000</pubDate></item><item><title>Re: Tools for Accelerating Python</title><link>http://amundblog.blogspot.com/2008/11/tools-for-accelerating-python.html#comment-4064586</link><description>&lt;p&gt;You forgot about Cython [&lt;a href="http://cython.org/" rel="nofollow noopener" target="_blank" title="http://cython.org/"&gt;http://cython.org/&lt;/a&gt;]. It somehow connected to PyRex and seems to be mice to use.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ryszard</dc:creator><pubDate>Sat, 29 Nov 2008 17:29:51 -0000</pubDate></item></channel></rss>