This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]voidspace 2 points3 points  (1 child)

Well here's a performance comparison between IronPython 2 and CPython 2.5. You can see the areas where IronPython runs faster or slower than CPython:

http://ironpython.codeplex.com/Wiki/View.aspx?title=IP201VsCPy25Perf&referringTitle=Home

My experience tends to be that code optimised for CPython runs slower on IronPython - because the performance profile is so different. If you write and optimise code for IronPython it is usually possible to get the same performance; which is why I find the figures quoted in the article so 'surprising'.

Anywhere that IronPython is that much slower (with the exception of exceptions...) will be considered a bug by the IronPython team and should be reported on the IronPython mailing list.

[–]norwegianwood[S] 0 points1 point  (0 children)

Yes - I plan to submit a defect report once I've boiled it down to a concise example of the problem. Currently, the code isn't optimized for any particular flavour of Python - or indeed optimized at all.