Am I expecting too much, or is ORD very slow compared to Inroads/Geopak? I mean, with all of the resources it appears to be loading, it takes 5+ minutes to open the first design file. Every DGNLIB from my client workspace has to load, and with all of the settings, there are a lot of DGNLIB files. Subsequent files don't take as long, but it is definitely slower than I am used to.
It feels as if there is lag to everything I want to do, every setting I want to change.
I am using a client workspace, so this isn't anything I set up myself. Are there any settings I should look into, or any way to speed it up?
Windows 11, 32 Gb RAM, if that makes any difference.
Thank you.
Hi Mary,
MaryB said:I am not using ProjectWise.
Although usually PW is treated as a reason of slowness, maybe in terms of managing workspace it would help.
MaryB said:I am working over a VPN, which is, admittedly, slower than hardwiring to the network at the office.
Yes, network is slower than local access, VPN is slower than normal network.
I would guess that it can be the biggest reason, why ORD is slow. The workspace probably contains hundreds (or even over a thousand) files, but the most important are dgnlibs. How many are there? And the dgnlibs contains thousands of definitions, that all must be read.
I recommend to try to copy the workspace to local disk and to compare the difference.
MaryB said:but I wish there were a way that certain DGNLIB files could be loaded more on an "as needed" basis.
In my opinion civil team has tried to optimize how dgnlibs are loaded (like to filter dgnlib by its name, not only by variables), a question is whether existing workspace(s) are structured to be able to use these optimizations. "Ad hoc" loading sounds like good idea, and it is up to developer when data is queried and loaded from dgnlibs, but the problem of ORD is feature definitions complexity: To load complete feature definition requires to load "everything" ... levels, templates, annotations etc. On the other hand, to open and display file, no these definitions are required, because when used, the definition is copied to local file.
MaryB said:I had seen threads for years that ORD ran slower in general than V8i.
Yes, it's correct. And although every release brings some optimization, it's still quite slow product.
MaryB said:I guess I didn't really think much of it.
In my opinion the speed and time you mentioned are not normal, especially when talking about file opening. I can imagine, when there are hundreds of sections and something is changed in alignment, to update complete chain (corridor, annotations...) can take a huge amount of time.
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Hi Chuck,
caddcop said:We are currently working with Bentley on a complete revision to our Workspace
it would be great to share a summary or "best practices learned" from such project. I do not recall any such document available (but ORD is not the main product I work with), but I often use workspaces with long history, where probably plenty of things are obsolete or can be done better.
Regards,
Considering that this is their very first, freshly released ORD workspace, my hopes are not high...It look as if they have done good work to get what they have, but it's taken this long to get here so I don't expect updates any time soon.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
We are currently working with Bentley on a complete revision to our Workspace and there are a number of things that can be done with DGNLIB's that apparently speed up load times, but it requires recreating a number of DGNLIB's. It's possible your client's workspace is still using the older methodology. All you can do is hope that they will update the workspace to incorporate these changes.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
I am not using ProjectWise. I am working over a VPN, which is, admittedly, slower than hardwiring to the network at the office.The files are not complex. I have this delay even when creating/opening new, empty files to begin working.
I always open ORD from the desktop icon. After so many years before workset branding, I may never trust that just double clicking from Explorer would open the proper workspace...I am old.
We do not store workspace files locally because the work of keeping every machine updated with the proper copies of every client workspace for everyone who uses ORD is simply impractical. It is also MUCH easier to administrate those workspaces, with associated worksets, etc. from a central location on a server than to try to keep track of everyone's computer. Our IT department are generalists, without much CAD or CAD Admin experience (as far as I can tell).
I think some of it is an overabundance of client resources, and the fact that they all need to be loaded every time. I understand why that is, but I wish there were a way that certain DGNLIB files could be loaded more on an "as needed" basis. I am not going to need my sheet creation DGNLIBs for weeks, yet there they are, all two dozen of them, every time I open OpenRoads. File switching is much faster than initial opening, for which I am grateful.
I had seen threads for years that ORD ran slower in general than V8i. I guess I didn't really think much of it.