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: Module Performance Problem
Topic Summary:
Created On: 15-Feb-2008 06:10
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.
 15-Feb-2008 06:10
User is offline View Users Profile Print this message


Paul Miller

Posts: 376
Joined: 2-Oct-2002

Hi,

I have two modules, Module A and Module B. Module A links to Module B in that direction.

Both modules seem to be fine, they open and close very quickly, no abnormal problems observed until...

Module A has a view with a single trace column created by the Analysis Wizard. All it displays is the linked object UID's in Module B. When you select this view and scroll down, as soon as the fist outgoing link indicator comes into view, DOORS hangs for an unusually long time (minutes) as the trace script attempts to open Module B in the background and start displaying Module B's UID's in the trace column. This problem does not happen when selecting a complementary view in Module B that traces back to Module A.

Something very wrong with Module B when the trace script in Module A tries to open it. The trace code created by the Analysis Wizrds looks pretty much normal.

Has anyone else experienced such a problem and know what might be causing this?

-------------------------
Paul Miller
Specification Practices Specialist,
EuroCyber,
Melbourne, Australia.
Mobile: +61 (0)418 135 103
Web Site: http://www.eurocyber.biz
E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz
Report this to a Moderator Report this to a Moderator
 15-Feb-2008 20:35
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

You could posts both layouts and let us take a look.

You could also verify that the Mod-A View does not also have some OTHER layout that its working on.

- Louie
Report this to a Moderator Report this to a Moderator
 15-Feb-2008 23:24
User is offline View Users Profile Print this message


Gordon Woods

Posts: 35
Joined: 2-Mar-2007

Paul
"minutes" does seem very excessive. I have never seen this before (well not since the days of DOORS 3)

a couple of ideas spring to mind:

1. the wizards always produce layout dxl.

layout dxl is automatically refreshed everytime the focus moves. Usually this is not much of a problem and there is not a significant overhead; but the links may be causing some sort of interference

You could try converting from layout dxl to dxl attribute.

2. It might be that you are looking at previous versions rather than just the current version. Retrieving previous versions for every object does slow things down.

3. a third thought is that there is a lot of history in Module B so a baseline ( which saves the history in the baseline) could speed things up. But this would be apparent on opening module B.

4. Have you used the "any" or "specific" modules option in the selection? You haven't mentioned that you are using recursion so this may not be a factor.

5. delete the columns and try again with the wizards.- see if the problem is still there.

6. there could be a problem with the link module but that's a bit of a long shot - you could try rebuilding the links

7. finally post the dxl scripts or screen shots- it will be easier to spot anything awry.


Gordon Woods
gordon.woods2@baesystems.com
Report this to a Moderator Report this to a Moderator
 10-Mar-2008 12:39
User is offline View Users Profile Print this message


Martin Williams

Posts: 1
Joined: 25-Sep-2002

We have also experienced such a 'feature' whereby opening a module in the backgound due to a layout column takes a very long while when compared with directlyopening the module either via a link or via the main browser window.

I have wondered if it might be due to DXL attributes being acitivated. I have checked that the default view does not have a layout column nor dxl attributes visible. Is there a definition of when dxl attributes are activated - the dxl manual states 'the first time the attribute is accessed". In this instance I assume it is either when the attribute is displayed, used by dxl or the Formal Object Editor Window is opened. The latter would update all dxl attributes' values, in all cases it would be for all objects.

We try to ensure that the default for all users is that they open modules in read only mode - (via a link or 'double click' method). Wizard layout dxl does a open read so in theory they are the same.

We have kept an eye on and 'fixed' where necessary wizard generated code that has opened every module it thinks might be need to be opened - that is a different feature!

regards
Martin Williams

Thales
Aerospace Division
Crawley
Report this to a Moderator Report this to a Moderator
 10-Mar-2008 14:52
User is offline View Users Profile Print this message


Michael Grimsdale

Posts: 11
Joined: 27-Aug-2003

We have also experienced this problem, our solution is:
to change from layout dxl to dxl attribute, Use Tools, Support Tools, Covert Layout DXL to Attribute DXL.
If it is still slow check for deleted but not purged Objects this also slows down scrolling.:D
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.