Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Slow Accessing of Modules
Topic Summary:
Created On: 19-May-2008 13:39
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
Answer This question was answered by Alan Gooch, on Wednesday, May 21, 2008 12:28 PM

Answer:
Thanks Ron and Scott.
The clue was in the modules being opened by layout DXL and Rons' script pinned it down for me to one offending script on one module.
Removal of the layout DXL from the default view was a sensible move and should have been standard procedure anyway.
 19-May-2008 13:39
User is offline View Users Profile Print this message


Alan Gooch

Posts: 107
Joined: 30-Aug-2005

Using DOORS v71102

We are currently experiencing problems with opening modules and switching between module views, which I cannot definitely pin down to being network issues.

One module in particular takes up to five minutes to open (last week it was a few seconds). It IS a big module, but not the largest by any means). Sometimes it will open but with the infamous "<view list locked>" problem. Other times it will open but when I try to switch views I get a pop-up (eventually) saying "The list of views is currently locked".

User report that they are experincing similar problems at times with other modules, but by no means ALL modules and by no means ALL of the time.

I tried to open to main offending module very early this morning when the network was very quiet, and it was still very slow, hence my reluctance to blame the network.

This same module has a loyout DXL on the default view but, even when I manage to change the view to one without layout DXL, performance does not seem to improve.

I have searched the forums for a definitive answer to our problem, but most related postings are quite old now (possibly because of it being related to DOORS v7), so would be grateful for some fresh input.

Your suggestions are very much appreciated.
Report this to a Moderator Report this to a Moderator
 19-May-2008 15:12
User is offline View Users Profile Print this message


Scott Boisvert

Posts: 348
Joined: 14-Apr-2006

My first guess would have been a layout DXL column or a DXL attribute column in the default view.

I know you said you tried to change the view, and still had the problem, but just to clarify did you change the default view or just change the view. Try setting the default view back to the Standard view, close the module and try reopening.

If that improves performance, I would create a test view, adding each column to the view (layout DXL and/or columns containing DXL attributes) one at a time to find out which is the offending attribute/column.

Sorry I couldn't be more help other than pretty much restating what you probably have all ready done. You may want to contact support/though they will probably want a copy of the module to look at.

-------------------------
Scott Boisvert
Engineering Tools Administrator
L-3 Communications - Avionics Systems
scott.boisvert@l-3com.com
Report this to a Moderator Report this to a Moderator
 19-May-2008 16:28
User is offline View Users Profile Print this message


Octavian Stanescu

Posts: 39
Joined: 28-Feb-2005

Did you try to baseline? The history is increasing over time and baselining clears that history.
Report this to a Moderator Report this to a Moderator
 20-May-2008 08:34
User is offline View Users Profile Print this message


Alan Gooch

Posts: 107
Joined: 30-Aug-2005

We do regular baselines. The main module in question was last baselined a week ago.

Regarding layout DXL, I have created a separate view without the layout DXL and made this the default.
Early today (before other user were in) I opened the module quickly, switched to the problematic view and it was slow, which made me think that may be the problem.
However, I repeated it just now, with more users in and active, and both views opened quickly, which makes the findings inconsistent.
Report this to a Moderator Report this to a Moderator
 20-May-2008 13:33
User is offline View Users Profile Print this message


Scott Boisvert

Posts: 348
Joined: 14-Apr-2006

Not necessarily, look at your layout DXL. Does it close the modules it opens?

My point is this, alot of the lag with the layout DXL is that of opening and closing modules, at least from my experience. Sometimes what I've found people doing is they have the layout DXL open up a module in the background but it's never closed by the script, and it remains open in the background until the client is closed.

So unless you closed your client between these two tests, the first time you opened the module/switched views, the layout DXL opened all the modules, the second time all the modules the layout DXL opens could have all ready been open, which would be the reason for the quick switch the second time.

-------------------------
Scott Boisvert
Engineering Tools Administrator
L-3 Communications - Avionics Systems
scott.boisvert@l-3com.com
Report this to a Moderator Report this to a Moderator
 20-May-2008 14:59
User is offline View Users Profile Print this message


Alan Gooch

Posts: 107
Joined: 30-Aug-2005

Ah, I understand. The layout DXL DOES leave modules open in the background which may explain the speed of re-opening.

As the layout DXL has not changed in many a while, I don't think this is directly the problem. However, we HAVE created two new linksets from a new module to the two largest modules this week, which each contain over 100 links - although that's not a lot to be fair.

I tried deleting the linksets (and closing all my open modules via the Manage Open Modules menu option), and it made no difference :-(

Therefore it DOES appear to be connected with the opening of modules in the background, although I do not understand what has caused this to suddenyl be a problem with a script which has remained unchanged for nigh on four years.

Edited: 20-May-2008 at 15:22 by Alan Gooch
Report this to a Moderator Report this to a Moderator
 20-May-2008 15:47
User is offline View Users Profile Print this message


ron lewis

Posts: 650
Joined: 20-Sep-2004

If you try to instrument your layout dxl with something like the following code snippet you might get a hint at what is causing the problem.
Report this to a Moderator Report this to a Moderator
 20-May-2008 16:41
User is offline View Users Profile Print this message


Scott Boisvert

Posts: 348
Joined: 14-Apr-2006

Could be the increase in size of the modules that are opened or the number of module that are opend have increased. I'm assuming the script has something to do with links, so if a link was added to another module, that's one more module that needs to be opened.

-------------------------
Scott Boisvert
Engineering Tools Administrator
L-3 Communications - Avionics Systems
scott.boisvert@l-3com.com
Report this to a Moderator Report this to a Moderator
 21-May-2008 12:28
User is offline View Users Profile Print this message


Alan Gooch

Posts: 107
Joined: 30-Aug-2005

Answer Answer
Thanks Ron and Scott.
The clue was in the modules being opened by layout DXL and Rons' script pinned it down for me to one offending script on one module.
Removal of the layout DXL from the default view was a sensible move and should have been standard procedure anyway.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.