It seems that Karamba GH components are being “rendered” for the UI even when they are not visible. This means that the larger the Karamba-script gets, the slower it becomes to navigate. At some point, this actually becomes so slow, that it slows down the workflow.
The normal GH behavior is to only render components for the UI that are currently visible. The canvas redraw speed is close to 75fps when opening an empty GH document. With an exemplary 500+ component document, the canvas redraw speed remains at 75fps when zooming into an empty area. (Of course it gets slower in the denser areas)
When taking a Karamba file - for instance the Zollamtsteg from the Website - the redraw speed drops to 36fps. When duplicating (for demonstration purposes) the exemplary file, the fps are cut in half and so on.
I already talked about this issue with @curtisw, who said that this bug needs to be fixed by the plugin devs. @karamba3d, could you have a look at this? I believe Curtis knows where the bottleneck lies, we had a similar issue with the
This issue happens on macOS as well as Windows.