Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.albasani.net!news.stack.nl!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path: <john_ladasky@sbcglobal.net>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.005
X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'mrab': 0.05; 'subject:Python': 0.06; 'friday,': 0.09; 'portions': 0.09; 'replied': 0.09; 'rewrite': 0.09; 'to:addr:comp.lang.python': 0.09; 'runs': 0.10; 'cc:addr:python-list': 0.11; 'extension,': 0.16; 'itself,': 0.16; 'limiting': 0.16; 'numpy': 0.16; 'wrote:': 0.18; 'cc:addr:python.org': 0.22; 'header:User-Agent:1': 0.23; 'cc:2**0': 0.24; 'cc:no real name:2**0': 0.24; "i've": 0.25; 'possibly': 0.26; 'header:In-Reply-To:1': 0.27; 'chris': 0.29; 'code': 0.31; 'fixing': 0.31; 'subject:what': 0.31; 'subject:the': 0.34; 'problem': 0.35; 'received:209.85': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'subject:?': 0.36; 'should': 0.36; 'received:209': 0.37; 'itself': 0.39; 'days': 0.60; 'most': 0.60; 'within': 0.65; 'simulations': 0.84; 'subject:latest': 0.84; 'week!': 0.93; '2013': 0.98
X-Received: by 10.50.43.225 with SMTP id z1mr193489igl.15.1365151148134; Fri, 05 Apr 2013 01:39:08 -0700 (PDT)
Newsgroups: comp.lang.python
Date: Fri, 5 Apr 2013 01:39:07 -0700 (PDT)
In-Reply-To: <mailman.125.1365150463.3114.python-list@python.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=99.100.180.25; posting-account=aVGMWgkAAAB6mGKt34gyuFhFeGnfZNcf
References: <6ac24546-6cc6-4a01-9fa6-3b52d64484e3@googlegroups.com> <mailman.125.1365150463.3114.python-list@python.org>
User-Agent: G2/1.0
X-Google-Web-Client: true
X-Google-IP: 99.100.180.25
MIME-Version: 1.0
Subject: Re: JIT compilers for Python, what is the latest news?
From: John Ladasky <john_ladasky@sbcglobal.net>
To: comp.lang.python@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: python-list@python.org
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Message-ID: <mailman.130.1365160842.3114.python-list@python.org>
Lines: 18
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1365160842 news.xs4all.nl 6892 [2001:888:2000:d::a6]:35530
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:42804

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 m=
ost tedious code I run.  I also do molecular-dynamics simulations with GROM=
ACS, those runs can take over a week!

> 2) Rewrite some key portions in C, possibly using Cython (as MRAB suggest=
ed).

And as I replied to MRAB, my limiting code is within Numpy.  I've taken car=
e 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.=20