On 2013-04-05 09:39, John Ladasky wrote:
On Friday, April 5, 2013 1:27:40 AM UTC-7, Chris Angelico wrote:
1) Can you optimize your algorithms? Three days of processing is... a LOT.
Neural network training. Yes, it takes a long time. Still, it's not the most
tedious code I run. I also do molecular-dynamics simulations with GROMACS,
those runs can take over a week!
2) Rewrite some key portions in C, possibly using Cython (as MRAB suggested).
And as I replied to MRAB, my limiting code is within Numpy. I've taken care to
look for ways that I might have been using Numpy itself inefficiently (and I
did find a problem once: fixing it tripled my execution speed). But I would
like to think that Numpy itself, since it is already a C extension, should be
optimal.
Well, Psyco obviously wasn't optimizing numpy. I believe the suggestion is to
identify the key parts of the code that Psyco was optimizing to get you the 20%
performance increase and port those to Cython.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
an underlying truth."
-- Umberto Eco
--
http://mail.python.org/mailman/listinfo/python-list
