Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

Revision history [back]

The explanation for this is most likely the following: The 32bit code of OpenStudio 1.14 runs more slowly than the 64bit code of (independent) EnergyPlus 8.6 under Windows10 (64bit).

The rationale for this explanation is:

Running the same OSM with the OS 2.0 App (64bit) is completed within EP-runtime 01:57:23, while the EP-export-IDF from OS 2.0 has a runtime of 01:55:22 - very much as expected. As macumber showed in his experiment, OS 1.14 and OS 2.0 (64bit) will typically have almost the same runtimes. Hence it must be the 32bit code that creates the remarkable time increase.

The explanation for this is most likely the following: The 32bit code of OpenStudio 1.14 - along with the bundled 32bit EnergyPlus code - runs more slowly than the 64bit code of (independent) EnergyPlus 8.6 under Windows10 (64bit).

The rationale for this explanation is:

Running the same OSM with the OS 2.0 App (64bit) is completed within EP-runtime 01:57:23, while the EP-export-IDF from OS 2.0 has a runtime of 01:55:22 - very much as expected. As macumber showed in his experiment, OS 1.14 and OS 2.0 (64bit) will typically have almost the same runtimes. Hence it must be the 32bit code that creates the remarkable time increase.