Ticket #90 (new enhancement)

Opened 9 years ago

Last modified 9 years ago

Closing Viewer takes very long time

Reported by: michelpons Owned by: michaelhalloran
Priority: major Milestone:
Component: Viewer Version: Development
Keywords: Cc: michaelhalloran

Description

I have loaded in the Viewer a very large log file (10 Mbytes almost) obtained with COLTT 1.08.5 Build July 17, 2011. After checking a few things I am closing the Viewer by clicking on the red arrow in the upper right corner. It seems to take forever to close the application (shown as using close to 100% of the CPU). Since the Viewer is not intended to modify a log file, closing the application should be very quick: there is no save mechanism involved.

The zipped log file is slightly heavier than 256 Kbytes so I will provide it by other means.

The scenario is using TRAC #24: the UO has been inserted in the flowsheet, its ports have been connected to streams, then the UO parameters are looked at through Aspen Plus v7.1 generic view and then the case is saved.

Attachments

apmain_091311_094559.zip (181.7 KB) - added by michelpons 9 years ago.
Zipped log file obtained with COLTT v2.0 Build Sep 11, 2011
apmain_061812_124253.zip (200.2 KB) - added by michelpons 9 years ago.
Zipped log file obtained with COLTT 2.1 Build June 16, 2012 on complete scenario in A+ 7.1
apmain_061812_143126.zip (38.2 KB) - added by michelpons 9 years ago.
Zipped log file obtained with COLTT 2.1 Build June 16, 2012 and reduced scenario in Aspen Plus 7.3.2

Change History

comment:1 Changed 9 years ago by michelpons

  • Milestone set to 2.02

comment:2 Changed 9 years ago by michelpons

  • Cc michaelhalloran added

Just made a check with COLTT v2.0 Build Sep 11, 2011. Closing the Viewer still takes a very long time. See as attachment the log file used.

Changed 9 years ago by michelpons

Zipped log file obtained with COLTT v2.0 Build Sep 11, 2011

comment:3 Changed 9 years ago by michelpons

I have loaded the same log file in COLTT 2.1 Development Build (I did not re-create the log file using COLTT 2.1, I used the log file from COLTT 1.08.5). Like with previous versions, while loading the file which exhibits 117413 nodes, takes just a few seconds, closing the Viewer takes minutes (something like 5 minutes). That looks odd. As an action within the Viewer, I searched for \"calculate\" and no matches were found which is OK since the scenario did not call for a calculation step.

comment:4 Changed 9 years ago by michelpons

I have reproduced the complete scenario using COLTT 2.1 Build June 16, 2012. The log file obtained is, before zipping, 7.5 Mbytes large. The scenario implies dropping a UO on the Aspen Plus flowsheet, connecting two inlet ports and one outlet port, displaying the UO parameters through Aspen Plus generic parameter viewer and saving the file. To make some comparison I have also used COLTT 2.1 Build June 16, 2012 in Aspen Plus 7.3.2 using a reduced scenario: just dropping the UO on the flowsheet and exiting without saving. The log file is already 1.3 Mbytes heavy. For sure the UO has many parameters still. Looking at the log files, I think that they could be reduced to one-fith or one-sixth of their current sizes.

There are a lot of sequences as the following one:
Port Collection <B1> : Logging for IMarshal with GUID {00000003-0000-0000-C000-000000000046} is not supported by COLTT
Port Collection <B1> : Logging for IMarshal with GUID {00000003-0000-0000-C000-000000000046} is not supported by COLTT
Port Collection <B1> : Logging for unidentified interface with GUID {0000001B-0000-0000-C000-000000000046} is not supported by COLTT
Port Collection <B1> : Logging for IStdMarshalInfo with GUID {00000018-0000-0000-C000-000000000046} is not supported by COLTT
Port Collection <B1> : Logging for IExternalConnection with GUID {00000019-0000-0000-C000-000000000046} is not supported by COLTT
Port Collection <B1> : Logging for unidentified interface with GUID {4C1E39E1-E3E3-4296-AA86-EC938D896E92} is not supported by COLTT
Port Collection <B1> : Logging for unidentified interface with GUID {1C733A30-2A1C-11CE-ADE5-00AA0044773D} is not supported by COLTT

Almost every method call is accompanied by these. I can't recall why we decided to display these calls but their repetition is kind of boring and it may be useful to consider a configuration flag that lets the end-user decides to print these pieces of info to the log file or not. It is the only action I see as possible on COLTT side, the others being on the PME side (reducing the number of calls to getParamters for instance).

Changed 9 years ago by michelpons

Zipped log file obtained with COLTT 2.1 Build June 16, 2012 on complete scenario in A+ 7.1

Changed 9 years ago by michelpons

Zipped log file obtained with COLTT 2.1 Build June 16, 2012 and reduced scenario in Aspen Plus 7.3.2

Note: See TracTickets for help on using tickets.