[IronPython] pybench results for CPython and IronPython
luismgz at gmail.com
Sat Apr 21 07:55:35 PDT 2007
I also I agree with you two.
Boo is an extremelly nice and productive static language, and its
syntax is so similar to Python's that waisting time deciding what to
choose for a given task is almost non-sense.
I think the decision should be made based on platform and libraries to
be used mainly and, in any case, converting from python to Boo is
Note that performance-wise, Boo is still completely unoptimized, as
its author recently recognized.
It has for sure the potential to become as fast as C#, but so far its
development has been concentrated in completeness and correction (as
is the case with IP).
For me, the difference between python's dynamicity and Boo is simply
that python allows for a more exploratory way of development. But if
performance is paramount, moving part or all the program to Boo is
On Apr 21, 10:04 am, "M. David Peterson" <xmlhac... at gmail.com> wrote:
> I agree, Boo is a nice language, but given its foundation as a
> statically-typed language it's not exactly a one-to-one comparison.
> Of course you can always use the duck type capabilities to gain a
> similar dynamic effect, but even a Boo duck type doesn't provide a
> fair one-to-one as you still have to declare it as a duck type, and
> once you do, the performance advantage gained from the static
> compilation is obviously lessened.
> Anybody happen to know of a similar benchmark comparison between
> CPython and the duck type-based Boo equivalent? And has anybody taken
> the time to quantify how much benefit is gained in developer
> productivity due to the rapid prototyping and interactive capabilities
> provided to the .NET developer at runtime?
> If for no other reason (and there are quite a few other reasons), the
> fact that with IronPython I can quickly and easily move from idea >
> through the thought process > and into a working prototype in about
> the same amount of time it takes to open up Visual Studio and create a
> new project is worth each and every additional cycle, cycles which can
> easily be gained back by writing the production app in C# (or Boo, for
> that matter) once things have solidified into something a bit more
> production worthy.
> Just food for thought, but if we're going to compare apples and
> oranges lets at least take a bite out of the apple and peel the orange
> before making a determination as to which one is preferable, and why.
> On 4/21/07, Arman Bostani <a... at twinsun.com> wrote:
> > Thanks to Sanghyeon for running the benchmarks. To summarize his
> > results, it seems like IP is pretty good at: comparing simple types,
> > loops, function calls and float arithmetic. It performs pretty poorly
> > at almost everything else! I guess its time to convert critical code
> > sections to Boo.
> > -arman
> > > Date: Fri, 20 Apr 2007 23:02:49 +0900
> > > From: "Sanghyeon Seo" <sanx... at gmail.com>
> > > Subject: [IronPython] pybench results for CPython and IronPython
> > > With IronPython 1.1 released, I ran pybench for CPython and IronPython
> > > on my machine, and published the result here:
> > >http://sparcs.kaist.ac.kr/~tinuviel/pybench/
> > > py24, py25, ipy11 are raw pybench result files. ipy11-vs-py24 and
> > > ipy11-vs-py25 are comparing reports generated by pybench.
> > _______________________________________________
> > users mailing list
> > u... at lists.ironpython.com
> M. David Petersonhttp://mdavid.name|http://www.oreillynet.com/pub/au/2354|http://dev.aol.com/blog/3155
> users mailing list
> u... at lists.ironpython.comhttp://lists.ironpython.com/listinfo.cgi/users-ironpython.com
More information about the users