On my machine it is about 40% faster in 2.0 than 1.1.1 but still about 2x slower than CPython:
Current 2.0 bits: (0.930676873737, 3.53996855746) 1.1.1: (1.07254462509, 6.25653658496) CPython 2.5.2: (0.83603013790858893, 1.8179086308455403) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sanghyeon Seo Sent: Sunday, August 03, 2008 3:47 AM To: Discussion of IronPython Subject: Re: [IronPython] Performance issue when calling a function with **kw 2008/8/3 Asaf Kleinbort <[EMAIL PROTECTED]>: > Calling a function with **kw takes about 10 times more time than calling a > function with a simple dictionary. The difference exists also in cpython > but there the differences is hardly noticed. > > Does anyone know if this is going to improve in version 2.0? As far as I can tell IronPython 2 does not improve this case. However, IronPython 2 does improve *seq case, more than a factor of two, compared to IronPython 1. I have a plan to do a comprehensive benchmark of call sequences for CPython, IronPython 1, and IronPython 2, based on callbench developed in PyPy. Ah, procrastination... -- Seo Sanghyeon _______________________________________________ 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
