![]() |
Telelogic DOORS (steve huntington) | ![]() |
Topic Title: string text(Column c, Object o) very slow in batch mode / non-visible modules Topic Summary: Created On: 11-Sep-2008 14:35 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hello everybody,
today I was modifying an existing reporting script, which works very well on open modules, such that it worked in batch mode. I was quite surprised that the script, which runs some 5 seconds on an open module, in batch mode took 5 minutes to finish. I was able to track down the bottleneck, which appears to be the string text(column c, Object o) perm, which seems to work an order of magnitude slower on invisible modules or in batch mode compared to visible modules in interactive mode. Did anybody experience a similar problem and knows a workaround? Thanks in advance, Peter |
|
![]() |
|
![]() |
|
I'm assuming you're using the text function because the column you are exporting is a DXL column? I didn't realize it slowed it down. I know for my export scripts I determine what the column has. Then either use the o.attrName"" notation or text(column, object) as appropriate.
I can understand why it'd be slower on DXL columns when the module isn't displayed. The value for each row hasn't calculated so it has to calculate it on the fly whereas with an open module it already has. ------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com Edited: 15-Sep-2008 at 13:26 by David Pechacek |
|
![]() |
|
![]() |
|
Hi David,
yes, that's the case. Yes, that would explain a certain extra-time. But I am experiencing something where the export in a file takes 20 seconds for visible modules and 15 minutes if the module is not visible. Regards, Peter |
|
![]() |
|
![]() |
|
Check the DXL in that column. It may be opening and closeing other modules for each object. I've experienced something similar in the past.
What I did is create a new view with a different dxl for that column that did not close the modules, then when the script was completed just parsed the database and closed all open module. You just need to put a warning on the script that states to save all work prior to running as all open modules will be closed. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
Hi Scott,
the DXL is quite simple, just concatenating two attribute values in one line. Peter |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.