![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Performance problem when module not visible Topic Summary: Performance problem Created On: 1-Apr-2005 22:24 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I have a script that is pulling an attribute from the source modules of incoming links. When I open the source modules with the display flag set to false, performance is extremely slow. If I change the display flag to true and have the source modules displayed, performance is acceptable. I would prefer not to have the source modules displayed, does anyone have a suggestion or know why there is such a big difference in performance just because the module is visible?
I have attached the code for reference. Thanks, Polly |
|
![]() |
|
![]() |
|
This is attribute DXL.
Code looks good, specifically setting the AttrDXL to -1 rather than setting it empty, since setting it empty is a flag to continually update it, which WILL cause performance to drag. What's this "setCacheState_" stuff all about? I'm curious. Try commenting it out. After opening the module, try the following code: string Value int CountObjs = 0, CountNulls = 0 for obj in entire current module do { CountObjs++ Value = obj."MyAttrDxl-Name" // insert attr name here if (null Value) CountNulls++ } ack(CountObjs "\t#Objects\n" CountNulls "\t"#Null values") Run this when opening invisible, and also for visible. If you get different results let us know and we'll try to go from there... - Louie |
|
![]() |
|
![]() |
|
Try using the actual attributes name instead of attrDXLName.
------------------------- Regards, Richard Good |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Performance problem when module not visible
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.