TuneUp delivering total nonsense results?

Packages
1

Hi folks,

I built a script which executed rather slowly (~50 seconds) when being used with the Dynamo Player in Alias. So i wanted to investigate, and ran it in Dynamo, using TuneUp for the performance analysis. I rebooted my computer, started Alias, went to Dynamo, ran the script. The script claimed to be done “Run completed” after 10 seconds. UI was responsive, but I couldn’t see any result in the 3D viewport, or any node output. Also, TuneUp wasn’t showing anything.
After about a minute, the 3D viewport was filled with the geometry, and TuneUp presented its result, claiming my script would have executed in 63 ms (lie??).
Okay… so slow 3D renderer, or what?

Switched off all “Preview Geometry”, made changes to all inputs of the script, to force it to be completely re-executed. Script takes about 50 seconds until “Run complete” now. Odd. TuneUp still with a similar result (~83 ms).

Also it seemed, that some warnings from some nodes weren’t cleared. Cleared the warnings by dismissing them, changed every script input, to force a complete new calculation. Takes about 50 seconds. Now TuneUp claims the whole script took over 3 minutes (189727 ms). :zany_face:
Most expensive operations:
2 times point creation on 2 curves (about 400 points in total), and getting those result from the list (First.Item and Last.Item), suspiciously all taking about 47.5 seconds each. :face_with_monocle:

As this seems to be clearly not working as expected: any advice on how to get better / more stable results from TuneUp?

EDIT: Dynamo version 3.4.2.7731, in Alias 2026.0.

Thanks,
GG

TuneUp-result
TuneUp-result3440×1440 353 KB

2

Yes - the graphic displays are out of process from the calculations. This is why Dynamo can be navigated while ‘running’. In a Revit context that isn’t the case.

The other thing not taken into account is the lag while the asynchronous API calls are made to Alias. The nodes have technically finished in many cases, but as the response isn’t back from Alias yet you’re still seeing the delay. This can cause REALLY awkward results similar to the 47424 millisecond execution time for your List.LastItem node.

For testing performance I generally recommend testing time in a sandbox environment, with as many interop removed as possible (so in this case no Alias nodes at all).

3

Thanks, Jacob, I will give that a try, and let you know how it goes!