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: DOORS performance problem
Topic Summary:
Created On: 7-Apr-2003 22:13
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 Deniz Akkor, on Friday, April 11, 2003 11:52 PM

Answer:
Pete,

Thank you for your reply. I have done more research on this performance issue. I found the reason why the importing process was slow. The end user was putting the cursor on the first object (row) or in the middle somewhere in the module when she started the importing process. The importing from XL spreadsheet into DOORS is much much faster if we run the DOORS import function from the last object.

Here are more tips that help to do importing process faster.

1. Make sure that the cursor is on the last object (row) when you append new data from excel into DOORS

2. Make sure that the column headers in the spreadsheet match attributes in the importing Module.

3. If the spreadsheet has the Absolute Number in it, define that as the "key" when you import the spreadsheet. The records with matching absolute numbers will be updated in a much faster way.

4. When you export to excel make sure that you have the absolute number column to be used. Later on, when you import the excel file to update the module, the absolute number columns will speed up the importing process. Therefore, use the absolute number as the unique identifier and change in the object text will be updated in DOORS faster.

5. If you have large history file in the importing module, you may run out of virtual memory when you do importing. Baseline the module just to erase the "current" history file; this may solve your module-is-too-big issue.

6. In order not to have "Object Text is too big" error when you import the spreadsheet into a module, make the "string" attributes size not more than a natural size limit (430 characters).

7. If a spreadsheet has been imported, and you subsequently change it, you can update the imported data by re-importing the file using the Update existing objects option.

Deniz
 7-Apr-2003 22:13
User is offline View Users Profile Print this message


Deniz Akkor

Posts: 18
Joined: 26-Feb-2003

The importing of spreadsheet is very slow from excel to DOORS. Especially it is very slow when we append or update data from excel to an existing DOORS module.

Here, what I found related this problem in Telelogic's web site.

1. Large numbers of links can cause performance difficulties - again before creation of large numbers of outgoing or incoming links consider whether they are really necessary

2. Large modules that are not baselined on a fairly frequent basis will affect performance. Since Doors records all the changes made, history files can become very large. Baselining locks away the current history and starts a new history log

3. DOORS data is sent in small packets between the client and the server. This means that good ping times are essential to gain optimal performance.

4. Telelogic recommends in their web site that the ping times should not exceed 50ms between the DOORS client and server. However, per Telelogic technical support on the phone, the ping times should not exceed 10ms.

5. Overuse of the edit-share option can degrade performance. Every edit-shareable section creates a new file in the database that needs to be loaded.

In large modules, it is recommended that edit shareable is set up at either level 1,2 or 3. If you use edit-shareable mode you should consider opening each module in full edit mode and doing a save on a periodic basis - this will roll the contents of the small files in the database into a larger file and improve performance.

6. Large amounts of OLE and pictures can affect a modules load time. To improve performance in this area an entry can be made in the door.ini file that will limit the number of OLE’s that are loaded at any one time in a DOORS module.

Open the doors.ini file (On NT and Windows 2000 this is located in the WINNT directory) Add the following entry: OleOpenLimit=5. Then save the Doors.ini file.

This means that only 5 OLE’s will ever be loaded in memory in the DOORS module at any one time. 5 is a good number because it’s unlikely that you could fit any more OLE’s on to the screen.

7. Removing the Network Server Monitor from the system tray may also improve DOORS performance on sites that are experiencing problems. The Network Server Monitor is the square blue icon that appears in the system tray and flashes when data is being sent between the client and server. To remove it select TOOLS>Options from the DOORS database Manager, Click on the settings tab, uncheck the ‘show network server monitor box’.

8. Large tables or large numbers of tables can again slow down performance - think about whether the use of a table is really necessary or appropriate before implementation

9. A memory intensive DXL script will not release memory after being run.
Exit DOORS to release memory.

10. When Scrolling through a module that has a series of objects that have object heading only, the display will refresh every time a new object becomes current. This significantly reduces scrolling performance. This problem is further aggravated if suspect link columns are displayed.
Decrease the vertical height of the formal module window, thus reducing the amount of text that needs to be redrawn with each screen refresh.

11. Heavy use of impact/trace or attribute DXL columns in views can cause performance to slow down.

12. Users may find that removing the Explorer pane from a default view for a module may reduce load times for a particularly large module.

13. Unnecessary triggers at open or close of module can slow down performance. Consider the implications of using triggers before implementation.


If you have any suggestion to improve the importing spreadsheet to DOORS, please feel free to add this list.

Deniz
Report this to a Moderator Report this to a Moderator
 8-Apr-2003 00:52
User is offline View Users Profile Print this message


Pete Kowalski

Posts: 301
Joined: 7-Feb-2003

Deniz...

I find breaking a huge CSV file into smaller chunks go much faster when updating a large module.

Pete

-------------------------
pete.kowalski(at)motorola.com
Report this to a Moderator Report this to a Moderator
 11-Apr-2003 23:52
User is offline View Users Profile Print this message


Deniz Akkor

Posts: 18
Joined: 26-Feb-2003

Answer Answer
Pete,

Thank you for your reply. I have done more research on this performance issue. I found the reason why the importing process was slow. The end user was putting the cursor on the first object (row) or in the middle somewhere in the module when she started the importing process. The importing from XL spreadsheet into DOORS is much much faster if we run the DOORS import function from the last object.

Here are more tips that help to do importing process faster.

1. Make sure that the cursor is on the last object (row) when you append new data from excel into DOORS

2. Make sure that the column headers in the spreadsheet match attributes in the importing Module.

3. If the spreadsheet has the Absolute Number in it, define that as the "key" when you import the spreadsheet. The records with matching absolute numbers will be updated in a much faster way.

4. When you export to excel make sure that you have the absolute number column to be used. Later on, when you import the excel file to update the module, the absolute number columns will speed up the importing process. Therefore, use the absolute number as the unique identifier and change in the object text will be updated in DOORS faster.

5. If you have large history file in the importing module, you may run out of virtual memory when you do importing. Baseline the module just to erase the "current" history file; this may solve your module-is-too-big issue.

6. In order not to have "Object Text is too big" error when you import the spreadsheet into a module, make the "string" attributes size not more than a natural size limit (430 characters).

7. If a spreadsheet has been imported, and you subsequently change it, you can update the imported data by re-importing the file using the Update existing objects option.

Deniz
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.