What if you NGEN the executable produced by pyc?
JIT can make startup expensive, and you're probably getting the adaptive
interpreter when running against ipy.exe.
On Thu, Sep 2, 2010 at 10:03 AM, Doug Warren doug.war...@gmail.com wrote:
That is the case, I made the change you suggested and it
That did it, thank you. My ignorance at the .NET framework shows itself.
with the test app it now executes at around 0.88 seconds vs the 1.6 for the
script version. And I feel silly for spending some time adding a splash
screen to the app as it just disappears in under a second.
On Thu, Sep 2,
The only thing I can think of is if you're on a 64-bit OS then ipy.exe is a
32-bit
EXE and the EXE you compiled is platform neutral - so it'll load on the 64-bit
CLR.
If that's the case you could use pyc.py with /platform:x86 and you should get
the
same behavior as ipy.exe.
Other than that
