Search in Dynamo Revit is PAINFULLY SLOW

revit

#1

For some reason, Dynamo running in Revit has EXTREMELY slow search performance - but only intermittently. I often have to wait several seconds for every letter i type in either the left-hand library search or right-click search. This makes Dynamo extremely painful to use. This has been true for at least the last year through various updates. Strangely, search in Dynamo standalone does not suffer from the same lag. Sometimes a simple search will take up to 30 seconds after typing, showing a spinny wheel until search results show up.

in the gif below you’ll see I can type an entire phrase before the dialog updates and returns results. This is not even close to how bad it can get:


#2

Could you share a list of your installed packages? We had a similar observation where a recent version of Clockwork was installed together with an outdated version and that was possibly creating some conflicts and leading to slowdowns.


#3

Thanks Dimitar - I’ve uninstalled a bunch of old packages, we’ll see if it makes a difference.


#4

Thank you for the report, we are working on it.


#5

I’ve also experienced the same problem, not just in v1.3. I assumed it might be that we have our packages on a network location and causing some latency issues, but thought this would only slow down initial opening time of the Dynamo application.


#6

You could also try disabling your Revit addins (except for dynamo ofcourse) and then try again. I had the same problem with Revit 2015, but after disabling most of my Revit addins everything was back to normal in terms of speed.


#7

deleting old packages seems to help but I haven’t used it extensively enough to be sure that it’s made the difference.


#8

I’ve experienced this as well with no additional packages installed. Dynamo has the problem. Hopefully this can be fixed because at times, it’s really painful. It can also be especially embarrassing if you’re giving a tutorial!


#9

I’ve been experiencing this with a new install of Dynamo 2.0.0 that has no additional packages installed. I’m therefore assuming that Revit Add ins may be the cause.


#10

Move your packages to either your local disk or a network share that is of minimal drive size (100mb?) and see if that helps.

Also can you confirm if you’re running in automatic mode?


#11

I have the same problem, but only with Dynamo 2.0 Not with the earlier versions < 1.3.2. I hope they find a solution soon :frowning:


#12

Where are your packages saved? What packages have you installed?


#13

The packages are installed at the default location. I have not changed that. I have the following installed:

  • archi-lab
  • Clockwork
  • DanEDU
  • Data-Shapes
  • Lunchbox
  • Rhythm
  • SteamNodes

Hope u have something for me to try and speed things up.


#14

Confirm that all those packages have already been updated for 2.0. If you’re having speed issues t may be due to the conversion from 1.x to 2.0 hogging resources.


#15

I can say that DanEDU for one have been depricated and replaced by Orchid (Which is updated for 2.0)


#17

As @Jonathan.Olesen writes is DanEDU deprecated and being replaced by the Orchid package.

The Orchid package has been reset lately and must be installed from Github repository

You may download the package from inside Dynamo or the package manager site (https://dynamopackages.com) but when the package is installed, only one node is available. This node will give the instruction and open the GitHub repository site for the user in a web browser.


#18

I believe the Bakery package does the same.


#19

@Luke_Johnson does it slightly differently, he provides a zip file. That method has the drawback that he needs to upload a new package when he updates the content. My method gives the advantage that I never ever more need to do anything. Everything is maintained from Github :slight_smile:

What is even more sophisticated is that I now can maintain two different parallels, one for dynamo +1.3.0 and one for dynamo +2.0.0 series. As you might know, +1.3.0 supports up to dotNET 4.6 and +2.0.0 supports dotNET 4.7.

It is not possible to maintain two parallels in the current settings at the package site if you want to have the same package name!


#20

@erfajo another option is for you to upload some kind of loader which grabs your package from github when run in the graph or checks for its existence before redownloading.

I’m not sure how this would work yet as I have not seen any examples in dynamo’s context, maybe flux.io’s package -

but there are plenty of examples on npm like selenium-standalone which requires an install step after getting the package.


#21

Is this something an extension could come in handy? Or maybe implemented into the Package Manager itself considering the pkg.json file already has a “repository” property. Some Nuget-ish Dynamo package manager kind of thing.