There is a performance hit when opening files from our ProjectWise datasource, and when using certain tools such as Place Beam and Place Column.
The OpenBuildings Designer Managed Workspace was configured so that specific ProStructures configuration variables pointed directly to ProjectWise folders:
- The primary ProStructures regional folder, in this case USA_Canada_Imperial, was defined by _PS_WORKSETSTANDARDS and pointed to the local ProjectWise cache at c:\pw_workdir\project-us\dms02563\
- However, variables that point to sub-folders under USA_Canada_Imperial, and are by default defined as child variables of _PS_WORKSETSTANDARDS, were modified to point directly to ProjectWise instead:PS_COMBISHAPES : Application = pw://project-us.pw.bentley.com:project-us/Documents/Standards/Managed WorkSpace/OpenBuildings Designer/Configuration/WorkSpaces/Standards/ProStructures/USA_Canada_Imperial/Shapes/CombiShapes/*/PS_ROOFWALLPANELS : Application = pw://project-us.pw.bentley.com:project-us/Documents/Standards/Managed WorkSpace/OpenBuildings Designer/Configuration/WorkSpaces/Standards/ProStructures/USA_Canada_Imperial/Shapes/RoofWall/*/PS_USERSHAPES : Application = pw://project-us.pw.bentley.com:project-us/Documents/Standards/Managed WorkSpace/OpenBuildings Designer/Configuration/WorkSpaces/Standards/ProStructures/USA_Canada_Imperial/Shapes/UserShapes/*/PS_WELDSHAPES : Application = pw://project-us.pw.bentley.com:project-us/Documents/Standards/Managed WorkSpace/OpenBuildings Designer/Configuration/WorkSpaces/Standards/ProStructures/USA_Canada_Imperial/Shapes/WeldShapes/*/
This resulted in a performance hit since the files in these four folders, which account for 707 of the USA_Canada_Imperial folder’s 1211 files (58%), were transferred and reviewed during the DGN file load process. Note that performance would be impacted even when working in Legacy mode since the ProStructures content is always available to allow Legacy members to be upgraded to ProStructures members at any time.
To address this performance issue the ProStructures content can be stored and accessed locally instead. In addition to a performance benefit, it may provide a cleaner layout for the ProStructures portion of the configuration.
In this example we are using $(SYSTEMDRIVE) to locate the \ProgramData folder which is normally created on C:\ but may located elsewhere:
_PS_STANDARDS_NAME = USA_Canada_Imperial_PS_WORKSPACESTANDARDS = $(SYSTEMDRIVE)/ProgramData/Bentley/OpenBuildings CONNECT Edition/Configuration/WorkSpaces/Building_Examples/Standards/ProStructures/$(_PS_STANDARDS_NAME)/ %lock _PS_WORKSPACESTANDARDSPS_SHAPESDATABASES > $(_PS_SYSTEMROOT)Shapes/AISC_Imperial.mdb%if exists ($(_PS_WORKSPACESTANDARDS)*.cfg)%include $(_PS_WORKSPACESTANDARDS)*.cfg level WorkSet%endif
The four sub-folders mentioned above were redefined as child variables of _PS_WORKSPACESTANDARDS mirroring a delivered configuration: PS_COMBISHAPES = $(_PS_WORKSPACESTANDARDS)Shapes\CombiShapes\*\PS_ROOFWALLPANELS = $(_PS_WORKSPACESTANDARDS)Shapes\RoofWall\*\PS_USERSHAPES = $(_PS_WORKSPACESTANDARDS)Shapes\UserShapes\*\PS_WELDSHAPES = $(_PS_WORKSPACESTANDARDS)Shapes\WeldShapes\*\
See also: Configuration Changes to Support ProStructures Interoperability