I have a problem. Sometimes OBD will crash without any warning. All my projects are very big. > 10GB on third parties files. And when I want to place a pipe or a valve, it took a 8-9 seconds to show up the Place component menu. I think there must be a good investigation why OBD is slower. Is it the system I have to invest, or the motor of OBD isn't good enough for windows 10/11.
It feels like in the early days using a desktop with pentium 2 speed.
See also related forum post https://communities.bentley.com/products/building/building_analysis___design/f/aecosim-speedikon-forum/240151/openbuildings-connect-edition-is-slower-than-v8i-for-the-same-computer
| How frequently will feature be used? | Several times a day |
| How much time will you save? | half a day of work |
I agree with you all. OBD is globally slow. As Channel Partner I make a lot of demonstrations. I'm trying each time to have the cleanest computer I can but it remains slow...
Yes .... OBD Update 10 is sluggish.
Seems the new Pro Steel tools/features really slow down the structural models.
Also, seems to need to 'Load the Assembly Library' every time I open a file.
Surely this shoud be loaded at the start of a work session, then remain in RAM as long as OBD is open/in use
I have upload my files for investigation. And I think the problem is the speed how OBD read/write the datagroup. Casenumber is CS0116245.
This is a longstanding issue with OBD/Aecosim before it.
Unless you are working on C drive(no network install) with an out of the box installation and no customisation it is just pathetically slow. takes seconds to activate tools, seconds to de activate and switch tools. Catalog is so slow.
Working on any standard project, on a network, using custom components and datasets, so slow... I have had Bentley developers agree with me. I have complained about this for years but nothing has been done about it.
OBD crashes so many times a day. Crashes when changing tools, crashes when modifying components, crashes when cutting DV's or cacheing views.
I have demnstrated several times, lodged so many service tickets over the years
@All: Andy Parinussa has been in contact with Bentley support and provided project data. Support investigated and found that the file contained ACIS bodies. Improvement could be achieved by running the Convert keyin so that they are changed to Parasoild bodies.
Bug 1210561 "Performance issue while navigating between files and working with them" has been filed as some issues with file opening and working with them and also zooming in & out remained.
We will keep you updated with further information about improvements.
Hi Andy, hi Johan,
Thanks for sharing your comments and ideas about OBD performance. Please provide data and detailed explanations to Bentley support via Cases in ServiceNow. The better you describe the issues you are facing, the better support can reproduce them and report them to product management and development to work on them.
Regards, Johannes
Even though my projects are much smaller I often run into problems with speed as well. I agree that there must be serious investigation into what makes OBD so slow. Certainly because most times my CPU/GPU/RAM are far from their max capacity (usually only single core maxed out).
I may share my project, for developers to test the system