I have a scenario where I have many geo COMPs with a variety of internal layouts. I am generating paths to a sub chop in each of these objects, via an op FIND dat, and then feeding this into a join CHOP to collect xyz positions from each into one big chop for instancing.
@ 150 selected chops, the join chop’s performance degrades quite considerably coming in at around 16 ms per cook. I would have just assumed this is necessary overhead, except I am able to cut the cook time down by a little over 16x by building my own custom “join chop” using a script CHOP:
I should note as well, that I am providing the paths using a dat’s .col() method. Not sure if this is relevant, but my script CHOP approach uses it as well.
While it’s not a biggie to write a few lines of code for me, this optimization might be applicable to other nodes as well like in script DAT’s which are considerably more expensive than their compiled node equivalents… so I figured I’d mention it here in case there’s something to be gained across the board!
Here’s my test file:
joinChopOptimizationRequest.1.toe (8.2 KB)