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: memory management
Topic Summary:
Created On: 16-Jun-2004 14:50
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.
 16-Jun-2004 15:29
User is offline View Users Profile Print this message


Paul Tiplady

Posts: 176
Joined: 28-Oct-2003



<< Is the memory cleaned after my dxl script has finished? >>


No. DOORS is really bad at cleaning up, until it finally exits, when it lets go of all the memory it's grabbed.


<< Is there some good practice on how to be economical with memory? I set every skip = null when I have finished with it. Is this enough? >>


There is lots of advice on how to be kind to your memory. Among the things to do are:
    1. Delete all your skips and buffers and DBs after use, and after setting them to null. Just setting them to null doesn't free up the memory, it just empties it.

    2. Use buffers instead of strings (and do all the set to null and delete things like above)

There are cleverer (well more experienced anyway ) guys and girls than me watching this forum who will doubtless give more detailed advice, but these little bits are at least a start (and will probably take you a while to implement anyway).

Enjoy!

Paul.

-------------------------


Paul dot Tiplady at TRW dot com
TRW Automotive

Edited: 16-Jun-2004 at 15:30 by Paul Tiplady
Report this to a Moderator Report this to a Moderator
 17-Jun-2004 10:24
User is offline View Users Profile Print this message


Pekka Mäkinen

Posts: 276
Joined: 18-Mar-2004

There's also a Technical Tip in the Telelogic Resource Center on this issue:
search for "Guidelines for Memory Management in DXL " by Jeremy Dick.

-------------------------
Pekka.Makinen@softqa.fi
SoftQA Oy -http://www.softqa.fi/
Report this to a Moderator Report this to a Moderator
 17-Jun-2004 20:56
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Judging from the Task Manager memory useage and test scripts that do lots of nothing often and times how long it takes; I make the following concusions:

[] Memory is "released" when modules are closed.
[] Memory is "unused" when the DXL/Dialog is closed.
[] Memory remains fragmented; there is no garbage collections.
[] Memory fragments are released to the system when DOORS closes.
[] Opening modules visible takes a LOT more memory than invisible.
[] Opening lots of modules will tax your memory and bring DXL to a crawl.

The memory fragment issue makes DOORS stuff run slower: the new DXL runs inefficiently in the garbage of the old DXL. When running some huge scripts (such as checking all modules) I tend to shut down DOORS afterwards.

Didn't know you should null out the Skips/Buffers before deleting them.

- Louie
Report this to a Moderator Report this to a Moderator
 28-Jun-2004 16:33
User is offline View Users Profile Print this message


Paul Tiplady

Posts: 176
Joined: 28-Oct-2003

Louie wrote:


<< Didn't know you should null out the Skips/Buffers before deleting them. >>



I was guessing -- it just seemed sensible, and probably (!) does no harm...

-------------------------


Paul dot Tiplady at TRW dot com
TRW Automotive
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.