got the information on our internal
tick usage.
Internally we've used the tick function
without parameters, which resulted in the discussed performance issues.
I did a test using tick(min, max) and
got a great performance boost.
Execution time went down from 1200s
to 51s, while the number of sent null messages and tick requests stayed
nearly the same.
Some ideas how this is possible?
If this perfomance stays the same in
further tests, i think we can delay the implementation of second generation
time management techniques.
Regards,
Michael
Dipl.-Inf. Michael Raab
Fraunhofer-Institut für Fabrikbetrieb und -automatisierung IFF
Virtuell Interaktives Training
Sandtorstr. 22, 39106 Magdeburg, Germany
Telefon +49 (0) 391/ 40 90 122
Telefax +49 (0) 391/ 40 90 115
address@hidden http://www.iff.fraunhofer.de
oder http://www.vdtc.de
Eric Noulard <address@hidden> Gesendet von: address@hidden
05/29/2009 11:18 AM
Bitte antworten an
CERTI development discussions <address@hidden>
An
CERTI development discussions <address@hidden>
Kopie
Thema
Re: [certi-dev] CERTI performance issue
2009/5/29 Michael Raab <address@hidden>:
>
> Dear all,
>
> some more information from our side:
>
>> How long does this simulation run (elapse time)?
>
> approx. 1200 s
>
>> 3 federates: are they all tree time regulating and time
constrained?
>
> Yes!
>
>> Elapsed (Wall Clock) Time :
>
> What do you mean? We have no real time application like a flight simulator.
> We're using CERTI to connect some discrete event simulation systems,
> in this case three instances of SLX ( FYI http://www.wolverinesoftware.com/
> ).