Python 3 about 10x slower than old python component

[AndersDeleuran]

@Bernd_Möller

Any ideas why?

Using .NET (e.g. RhinoCommon/rhinoscriptsyntax) in CPython (i.e. the Python 3 Script editor) is currently substantially less performant than using it in IronPython (i.e. the . NET version of Python used in the old GhPython and the new IronPython 2 Script components). See this topic:

Rhino 8 Regression: CPython/IronPython RhinoCommon Performance Is Worse

Hi McNeel, I’ve noticed that CPython scripts will perform substantially worse when implementing RhinoCommon than IronPython (presumably because of Python.NET) . And that the new script editor with IronPython performs slightly worse than GHPython (presumably because of the new editor, since they’re both running 2.7.12 .NETCoreApp). Here’s a quick demonstration making a whole bunch of Point3d within for loops: [2024-02-05 14_54_27-Grasshopper - 230801_ScriptsMillionPoints_00_] 230801_ScriptsMi…

@Bernd_Möller

Any way to get them to a similar speed?

I’m currently still using GhPython in Rhino 8 for production on anything that uses RhinoCommon. And then dabbling with the CPython component for things that are pure Python and uses PyPi packages. And kicking the tires on the new IronPython component as a future replacement for GhPython (e.g. in Grasshopper 2, which does not ship with/support GhPython, as far as I can tell).