TuneUp is in beta.
TuneUp is a view extension for analyzing the performance of Dynamo graphs. TuneUp allows you to see overall graph execution time, per-node execution time, and other helpful information about what's happening under the hood, e.g. nodes run in the current execution v.s. nodes run in the previous execution (which were skipped during the most recent graph run for optimization/ caching).
Here is a short demo of how to utilize it as of now (now loading from the Extensions menu):

Here is a mock up of the future design:

- VisualStudio 2022 or later
- .NET 8.0 Developer Pack
- Dynamo repository cloned and built on the same level of TuneUp repository which means your Dynamo repo and TuneUp repo should exist under the same parent folder.
- After a
Debugbuild of Tuneup one can expect:- Under
TuneUp\dist\TuneUp, there is a sample package wrapped up ready for publishing and adoption. This would be the un-optimized version. - Un-optimized package installed locally for [DynamoVersion] defined in TuneUp/TuneUp.csproj, under DynamoCore and DynamoRevit
- Under
- After a
Releasebuild of Tuneup one can expect: UnderTuneUp\dist\TuneUp, there is a sample package wrapped up ready for publishing and adoption. This would be the optimized version.
- TuneUp does not work with .dyfs (custom nodes) yet.
- TuneUp binaries are not semantically versioned and are not intended to be built on top of as an API. Do not treat these binaries like DynamoCore.
- TuneUp requires Dynamo 3.0 or higher for access to new extension APIs.
- When user have TuneUp open, after switching workspace in Dynamo, the first graph run does not give execution time and nodes order.
- Although it's not an issue by itself, TuneUp profiles the execution of graphs even if not showing on the extension bar.
- In some cases TuneUp may calculate incorrect execution times for nodes, we cannot reproduce this consistently, if you see this occur and can reproduce it please file an issue!
Please check out known issues before trying to setup testing.
- TuneUp targets .NET 10 and builds against the Dynamo 4.3 NuGet packages (
DynamoPackageVersioninDirectory.Build.props, the only place it is set), the latest released Dynamo. It ships built in to Dynamo 4.4. Use a Dynamo 4.x build to test it. - Download a Dynamo 4.x DynamoCoreRuntime from dynamobuilds.com, or build Dynamo from the Dynamo repository and use its
bin\AnyCPU\Releasefolder. - Copy all contents of the Dynamo runtime to
TuneUp\TuneUpTests\bin\Release\net10.0-windows\(orDebug\net10.0-windows\), except theBuilt-In Packages\packages\TuneUpfolder and the NUnit and test platform files (nunit*,NUnit3*,testhost*,Microsoft.TestPlatform*,Microsoft.VisualStudio.TestPlatform*), so the copy doesn't replace the TuneUp build or the test runner. - Copy
TuneUp_ViewExtensionDefinition.xmlfromTuneUp\TuneUp\manifests\toTuneUp\TuneUpTests\bin\Release\net10.0-windows\viewExtensions\ - Open the copied
TuneUp_ViewExtensionDefinition.xmland change the assembly path to..\TuneUp.dll - Remove
TuneUpfrom your Dynamo packages folder if you have it installed from package manager (otherwiseTuneUp.dllwill get loaded twice). This won't work well. - Launch DynamoSandbox.exe, then click
View-> Open Tune Upand use while a graph runs.
- Install NUnit3TestAdapter from VisualStudio->Extensions->Manage Extensions->Online.
- Open Test Explorer from VisualStudio->Test->Test Explorer. Now you should see a list of TuneUpTests.
- Click the target test to run or run them all.
- Or from the command line:
dotnet test TuneUpTests\bin\Release\net10.0-windows\TuneUpTests.dll. All tests run on one STA thread (TuneUpTests\Properties\AssemblyInfo.cs), as Dynamo's own WPF tests do.
TuneUp is built into Dynamo (extern/TuneUp in the Dynamo repository) and is no longer published to the Dynamo Package Manager (publish_to_package_manager: false in pipeline.yml). Releases are built from the internal mirror, and CILibrary opens the version bump PR against this public repository automatically (create_pr_release_to_public_master in pipeline.yml).
- Before the release, set the next version by hand in
TuneUp/manifests/pkg.json(version) andTuneUp/Properties/AssemblyInfo.cs. CI doesn't change either file, and with no Package Manager publish nothing overrides thepkg.jsonversion, so the package Dynamo ships reports whatever is in this file - Make sure the internal repository's master is in sync with public master
- Create a release branch on the internal repository, named for the bump type (e.g.
release/patch-7,release/minor-1) - Build the branch. CILibrary bumps the version in
pipeline.yml, signs the binaries, archivesTuneUp.zipon the Jenkins build, then opens a PR on the public repository with the bump - Review and merge that PR, so public master matches the released version
- Delete the release branch on the internal repository
- Copy the contents of
TuneUp.zipfrom the Jenkins build intoextern/TuneUpin the Dynamo repository, and open a PR there
The version in pipeline.yml must always be the latest released version; the release build adds one to it. If the automatic PR is not opened, create it manually with the updated version number in the pipeline file.