![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: memory management Topic Summary: Created On: 16-Jun-2004 14:50 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
<< 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:
There are cleverer (well more experienced anyway ![]() Enjoy! Paul. ------------------------- Paul dot Tiplady at TRW dot com TRW Automotive Edited: 16-Jun-2004 at 15:30 by Paul Tiplady |
|
![]() |
|
![]() |
|
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/ |
|
![]() |
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
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 |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
memory management
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.