Michael demonstrates a very good point: if the question is "perf?", the only useful answer is "experiment!". There are so many factors that go into it, down to the machine and the environment it presents, that it's generally quicker and more informative to write a simple program and take several measurements, than it is to try to speculate your way through it (obviously idiotic algorithms notwithstanding). As Michael points out, the speed difference is also non-uniform across the API, so even an algorithm that improves perf on one platform may regress it in another. It also follows, then, that you also should state the experimental conditions when you quote the numbers.
________________________________ From: [EMAIL PROTECTED] on behalf of Michael Foord Sent: Thu 8/14/2008 1:54 PM To: Discussion of IronPython Subject: Re: [IronPython] speed of ip compiled David Jensen wrote: > I would like to know if I write python standard programs and compile them into > an exe using IP1 or IP2, how much faster would it be than standard python. > > Also, how much faster is interpreted IP1 or IP2 than standard python running > as an interpreter? > > > Try it and find out. Earlier today I posted some micro-benchmarks showing how IronPython (compiling to exe will make no difference to execution speed with IronPython) is faster than CPython for some things, and slower for others. Michael > David Jensen > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/ http://www.trypython.org/ http://www.ironpython.info/ http://www.theotherdelia.co.uk/ http://www.resolverhacks.net/ _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
