Optimum Python Scripting and Iteration

[AndersDeleuran]

Here’s a few points to consider:

Python in Grasshopper (guid and geometry)

I’m not sure you will find a common practice as such, but I certainly prefer and advocate to implement RhinoCommon directly (for many reasons, if you search this forum and the old Grasshopper one you’ll find many topics related to this). Edit: A few of my key preference points for RhinoCommon: No GUID/coercing business. No missing functions/methods (i.e. that have not been ported). Better performance. Easy porting to C#/VB. OOP. That said, I still implement rhinoscriptsynax when interfacing…

And some simple tips on speeding things up:

Grasshopper Performance - Scripting Slower Than Native Components?

Specifically for GHPython, you can usually achieve considerable speed boosts on large inputs by not using type hints or the implicit Grasshopper cycle functionality (i.e. set the access type to List if you’re operating on a list and implement the loop yourself), and on large outputs by wrapping the data in appropriate Grasshopper types: [2021-04-29 09_09_17-Grasshopper Python Script Editor] Mesh Point Remap - multiThreadTest-minimumViableFile_GHPythonFixes_00.gh (1.6 MB) See this old thread…

Also, you might be able to multithread your code:

Multithreaded Python

Edit: Apologies, this is for GHPython (though the RhinoCommon points and multithreading are still valid). Hadn’t had my coffee yet