Apply Measure Now, very slow in some situations (large model and or large directory)

[DavidGoldwasser]

I loaded the "DEER_2017.osm" that ships with OpenStudio 2.4.3 into OS app and then went to Apply Measures Now. My measure directory is "nrel_published" from develop branch of measure repo.

The dialog came up in about 10 seconds and listed all of the measure, but when I select a measure (even if it is a measure without any arguments) it took 130 seconds before I could click run. My guess is this is measure manager working through all the measures. Once I have waited for this if I leave the dialog and come back it is very quick. None of the measure.XML files were updated during this time.

If I quit the app and the launch and re-load the model, it takes 120 seconds again when I first use apply measures now.

[ljbrackney]

+1. I've also seen sluggish performance in populating the measure list, popping up arguments, and being able to select run in recent builds.

[jmarrec]

Reproduced it in 2.7.1, windows 10, (recent Ryzen 1800X, 8-CPU, 32 GB RAM machine).

I'm not super familiar with the backend of Apply Now, but I'm guessing it's just the measure manager that basically loads the current model to compute potential user_arguments. Loading the "DEER_2017.osm" model itself in OS App takes a comparable amount of time. If that's it, then I'm afraid there's not much we can fix...