Definition becoming unusable due to <SessionTraceData>

[teocomi]

Dynamo version

1.0.0.1180

Revit version

2015 and 2016

Operating system

Windows 7 Pro SP1, 64GB RAM, Intel Xeon E5-1620 v3 @3.50GHz

What did you do?

I started experiencing several unjustified lags, Dynamo completely froze (and so Revit) for 10-20 minutes (or more) to complete actions that usually take a few seconds. It would happen when generating Revit elements, switching from Manual run mode to Automatic, other times just running the definition for the first time, other times just by creating a bunch of points.

I later on discovered that inside the .dyn file a huge portion of binary data was contained by a <SessionTraceData> tag (making up like 99% of the file size). I removed it and the file started behaving normally.

Is this a knows issue? Any way to avoid it in the short term?

The definition used generates a series of columns on several levels in Revit. But the issue started to happen even after breaking up the definition, eg just generating points:

Files: https://www.dropbox.com/sh/28gpnre12au9psy/AADJHHuoDcAPNkUUnsfxG0Zta?dl=0

[dimven]

Edit: The below was unrelated
I had this happen before and a clean install fixed it. The reporting is usually pretty behaved but for whatever unknown reason it goes out of control from time to time and brings my slow workstation hdd to a grinding halt.

You could also try to permanently disable the detailed reporting and see if that helps:

[teocomi]

Thanks for the tip @dimven , actually both reporting were already off.

[AndyDu1985]

This is a limitation of Revit, if you use Revit to create too many family instances, it will also take a lot of time.

[dimven]

While element generation in revit can be slow due to document regeneration, this is an entirely separate issue. It's related to Dynamo's element binding and in particular to the extremely slow de-serialization of the bindings saved in the *.dyn file. The above scenario becomes painfully apparent once you open a dyn that was previously saved after the creation of 1000+ elements in revit.

Because the binding serialization and de-serialization logic is part of DynamoCore, maybe it's a good idea to coordinate this with the Dynamo team. However, since there is no other issue open on element binding in the DynamoRevit repository, I suggest you leave this one open.

[AndyDu1985]

@QilongTang @mjkkirschner This issue is related to Dynamo's element binding algorithm. Do you have any comments?