Opened 12 years ago

Closed 12 years ago

#2074 closed defect (fixed)

Massive jump in timeTemplates

Reported by: Christian Schubert Owned by: anonymous
Priority: blocker Milestone: 1.9.0
Component: Code Generation Version: trunk
Keywords: dumpSimCode timeTemplates xml Cc: Adrian Pop, Jens Frenkel, Willi Braun, Lennart Ochel

Description

Hi,

since the commit

Revision 15072
Author: sjoelund.se
Date: Mittwoch, 6. Februar 2013 16:03:15
Message:
- Moved some of the debug information to reading the generated xml-file instead of compiling it into the C-code

timeTemplates is now 10 times bigger!

In case of Pendulum_20, I get with r15072

    timeFrontend = 3.5285706579897513
    timeBackend = 10.583999095187966,
    timeSimCode = 1.3463234181014607,
    timeTemplates = 7.726527522816053
    timeCompile = 7.073520501822674,

with r15071 I get

    timeFrontend = 3.486143325706232,
    timeBackend = 10.64029406391105,
    timeSimCode = 1.3594884331961614,
    timeTemplates = 0.7164336485675259,
    timeCompile = 9.581373052261595,

A 2 second decrease in compile time caused a 7 second increase in translation time.

It has probably to do with the new line in SimCodeMain.mo

Tpl.tplNoret(SimCodeDump.dumpSimCode, simCode);

I am very much in favor of reducing the compile time, but maybe this function can be improved?

Change History (3)

comment:1 by Martin Sjölund, 12 years ago

Owner: changed from Martin Sjölund to Christian Schubert
Status: newassigned

If you add a flag to disable dumpElementSource for the C-target, you generate a file ~18 times smaller for EngineV6 (107MB vs 5.8MB). This information needs to be preserved for the Dump target (and for debugging). For simulations in general it could possibly be ok to disable generating this info.

comment:2 by Christian Schubert, 12 years ago

Owner: changed from Christian Schubert to anonymous
Priority: criticalblocker

we have currently no resources for doing this. But it should be fixed before the 1.9.0 release.

comment:3 by Martin Sjölund, 12 years ago

Resolution: fixed
Status: assignedclosed

Actually, it's already been completed

Note: See TracTickets for help on using tickets.