Eclipse Community Forums: Epsilon » ETL Performance with Simulink

Help

Home

Home » Modeling » Epsilon » ETL Performance with Simulink

Show: Today's Messages :: Show Polls :: Message Navigator

ETL Performance with Simulink [message #1794830]

Fri, 07 September 2018 09:45

Stuart Hutchesson

Messages: 9
Registered: September 2011

Junior Member

I'm using ETL to extract the top level "context" from Simulink models into an EMF equivalent (Sub-system names and IO). The logic appears to work fine but is extremely slow for large Simulink models (to the point where I'm having to terminate the execution)

I'm using a rule such as this to find the top-level subsystems (which works fine) :

rule Subsystem2Service
    transform s : Simulink!SubSystem
    to t :  M!camcoa::Service {
    
    guard : s.parent == null    // Only process top-level subsystems
    
    t.name = s.name;
    
    for (c in s.children)
    {
        ("Found : " + c.name).println();
    }
}

I was then invoking @lazy rules to populate the relevant child objects. However the "s.children" loop takes an age to terminate for big models, and I'm wondering if this is essentially doing :

Block.all.select(b|b.parent = self);

Which would be very very inefficient for large model hierarchies.

The Matlab/Simulink scripting language include the ability to restrict the model search depth (and block type) when traversing the model :

find_system('sldemo_clutch/Unlocked','SearchDepth',1,'BlockType','Goto')

If the ".children" operation is being implemented as I suspect, would it be possible to have some means of restricting the search depth?? Are there any other tips/techniques to speed up execution time for this type of transformation?

Report message to a moderator

Re: ETL Performance with Simulink [message #1794846 is a reply to message #1794830]

Fri, 07 September 2018 15:24

Athanasios Zolotas

Messages: 52
Registered: November 2016
Location: York

Member

Hi Stuart,

Both .children and getChildren() are not implemented using the

Block.all.select(b|b.parent = self);

Instead, Matlab's find_system is used:

find_system(model,'SearchDepth',1,'Type','Block')

We need to do some profiling to find out possible reasons behind the slow performance on big models and we will come back to you.

Finally, it is of interest to filter the children based on their type as you suggest and we will work on that.

Report message to a moderator

Re: ETL Performance with Simulink [message #1795203 is a reply to message #1794846]

Tue, 18 September 2018 10:53

Sina Madani

Messages: 160
Registered: November 2015
Location: York, UK

Senior Member

I just wanted to add that in the event that you do use

Block.all.select(b|b.parent = self);

and find it slow, the latest interim build of Epsilon now has parallel versions of first-order operations, so this could be changed to

Block.all.parallelSelect(b|b.parent = self);

if that helps.

Report message to a moderator

Previous Topic:	Create spreadsheet as a model using ETL
Next Topic:	Problem Running Example Project

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Apr 20 00:34:11 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter