![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Slow access to a module Topic Summary: very large module with no attrDXL or layoutDXL columns Created On: 31-Jul-2008 06:10 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Our users have created a very large module with 21,200 objects. There is no attrDXL or LayoutDXL in the module. There are 19 user defined attributes for the objects. These are all displayed in the default view. All of the attributes are plaintext or boolean values. There are only 100 objects with outlinks and no inlinks in the entire module. There are no networking issues, the database is located on a local server. The machine I am using to run doors is quite powerful (Core2duo+2GB RAM)
We are receiving complaints (and I can confirm they are valid) that this module is very slow (2-3mins) to open in read-only mode, then very slow again (2-3mins) to go to exclusive edit mode. Frustrated users have split the module into about 10 smaller modules to get around the slowness and this works. Though I have never encoutered a module of this size I am confused because I thought DOORS wouldn't blink an eye at a module of such size. When the module is opening the DOORS Database window status bar says "Initialising Objects" for the majority of the 2-3mins. When going to exclusive edit mode the status bar says "Loading History" for about 15secs then "Initialising Objects" for the rest of the 2-3mins. One thing to note is that triggers have been active in this module. I don't know if this could be causing the issues or not. The purpose of the trigger is to prompt the user before selecting a module. But we have tested the module with triggers disabled and the slowness still occurs. Any ideas? The data in this module was originally stored in an Access Database which performed flawlessly. Users don't think DOORS is worth the frustration and lost time and are considering of reverting to Access. DOORS 8.0 Version 8.0.0.0 Build 80114 ------------------------- Peter Dawson Engineering Tools Support Group Boeing Australia Limited Edited: 31-Jul-2008 at 06:23 by Peter Dawson |
|
![]() |
|
![]() |
|
Hi Peter,
You mentioned 21,200 objects are in the Module. Please goto Module properties and check the History tab by selecting "Show History of" All. Since you dont have network issue & you have local instance.. Please try this.... "Modules need to be periodically baselined, a baseline takes all of the history stored on the module (the module + all the history has to be loaded upon opening a module) and puts it in the baseline and wipes the history clean. This can be a serious performance problem for a module if a baseline has not been taken for an extended period of time. It was stated that lack of baselining is one of the Top 5 performance issues Telelogic encounter when working with customers." Regards, Murugaraj S |
|
![]() |
|
![]() |
|
Can you also check How many number of deleted objects in the Module?
In Module window View -Show - Deletions. Just count how many number of deleted objects. Most companies rarely go through and purge out the database of deleted objects. If your module has deleted objects you still have to load them when opening the module, even though you can't see them. So if you have a large number of deleted objects that are not needed then this adds to your loading time. Better luck. Thanks Murugaraj S |
|
![]() |
|
![]() |
|
Is link history turned on?
------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
Thanks for your support but.
1) We baselined the module to remove history - no change to module slowness. 2) There are no soft deleted objects in the module 3) Link history is turned on. Could this be a problem? ------------------------- Peter Dawson Engineering Tools Support Group Boeing Australia Limited Edited: 1-Aug-2008 at 03:24 by Peter Dawson |
|
![]() |
|
![]() |
|
Has the module been split into shareable sections?
As you may know splitting the module into several shareable sections splits the module into several files. Doing this means it needs to load all these files to load the module and makes it much slower to load. I was of the understanding that once a module is split into several files it is irreversible even if the shareable sections are removed however Telelogic recently advised that if shareable sections are no longer required then reinstating the inheritance to all sections and saving the module should return it to one file and hence the load time should improve. ------------------------- Martin |
|
![]() |
|
![]() |
|
Peter
we have a module with just over 12,000 objects ( so half your size) However, loading on exclusive edit Loading objects ... takes about 5 seconds Loading history ... takes about 2 seconds Initialising objects ... takes less than 1 second total less than 8 seconds so 2-3 mins is rather long. So I suspect that here is something to do with the last stage and therefore I strongly suspect triggers if they were attribute level. When the modules were split what were the times then ? and were the triggers carried over? and if you haven't already In tools -> options -> settings select the Network Server monitor - this will monitor the network traffic between your computer and the server - it should be flashing green almost continually while the data is being loaded. If it is blue then there is no network traffic. ------------- Gordon Woods BAE Systems (Operations) Limited, Warton, UK gordon.woods2@baesystems.com |
|
![]() |
|
![]() |
|
If you recreate your links nightly, link history could certainly cause an issue. But I would think that would be erased with a baseline. Could be wrong though. ------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
Ok here is an update.
We have found that turning off the Module Explorer massively enhances the transition time between read-only and exclusive edit. We have also experienced slowness when deleting and adding objects to the module, but in this case as well there is no slowness when module explorer is turned off. It appears that there is a massive CPU burden involved with refreshing and rebuilding module explorer. Our default view for the module included the module explorer. When we removed it from the default view the load time for the module was reduced to 5-10 seconds. All 21K objects are at the same level which produces a really really long list in module explorer. Interesting hey? ------------------------- Peter Dawson Engineering Tools Support Group Boeing Australia Limited |
|
![]() |
|
![]() |
|
Over the years, I have developed several best practices to follow one being turning off the module explorer when processing modules.
I will always open modules in the background mode, load the Standard View and turn off the Module Explorer. Doing this will save me several minutes or even hour or two in the script execution. ------------------------- pete.kowalski(at)motorola.com |
|
![]() |
Telelogic DOORS
» General Discussion
»
Slow access to a module
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.