Editing IronPython (section)

== Performance ==
The performance characteristics of IronPython compared to [[CPython]], the reference implementation of Python, depends on the exact benchmark used. IronPython performs worse than CPython on most benchmarks taken with the [[Dhrystone|PyStone]] script but better on other benchmarks.<ref>{{cite web
| url=http://ironpython.codeplex.com/Wiki/View.aspx?title=IP26RC1VsCPy26Perf&referringTitle=Home
| archive-url=https://archive.today/20130119180607/http://ironpython.codeplex.com/Wiki/View.aspx?title=IP26RC1VsCPy26Perf&referringTitle=Home
| url-status=dead
| archive-date=January 19, 2013
| title=IronPython Performance Report
| access-date=2009-10-05
}}</ref>
IronPython may perform better in Python programs that use threads or multiple cores, as it has a [[Just-in-time compilation|JIT]] compiler, and also because it doesn't have the [[Global Interpreter Lock]].<ref>{{cite web
| url=https://wiki.python.org/moin/IronPython
| title=IronPython at python.org
| publisher=python.org
| quote=''IronPython has no GIL and multi-threaded code can use multi core processors.''
| access-date=2011-04-04}}</ref><ref>{{Cite web |url=http://jeffknupp.com/blog/2013/06/30/pythons-hardest-problem-revisited/ |title=Python's Hardest Problem, Revisited |access-date=2015-07-15 |archive-url=https://web.archive.org/web/20151031074238/http://www.jeffknupp.com/blog/2013/06/30/pythons-hardest-problem-revisited/ |archive-date=2015-10-31 |url-status=usurped }}</ref>