Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't know if you will really find speed improvement anecdotes that helpful, as your results are going to be highly dependent on your own implementation.</p> <p>That said, the following reference on <a href="http://www.mathworks.com/help/simulink/ug/how-the-acceleration-modes-work.html" rel="nofollow">How Acceleration Modes Work</a> might be useful to you.</p> <p>As described in this link...</p> <blockquote> <p>The Accelerator mode generates and links code into a C-MEX S-function. Simulink uses this acceleration target code to perform the simulation...</p> <p>...the model methods are separate from the Simulink software and are part of the Acceleration target code. A C-MEX S-function API communicates with the Simulink software, and a MEX API communicates with MATLAB. The target code executes in the same process as MATLAB and Simulink.</p> </blockquote> <p>The link goes on to describe Rapid Acceleration, as such:</p> <blockquote> <p>The Rapid Accelerator mode creates a Rapid Accelerator standalone executable from your model. This executable includes the solver and model methods, but it resides outside of MATLAB and Simulink. It uses External mode (see Host/Target Communication) to communicate with Simulink.</p> </blockquote> <p>(Note that the actual link has some nice diagrams that help to illustrate this architecture).</p> <p>I think that there are a few important things to takeaway from these descriptions. First, in Accelerator Mode, code is only generated for the model methods; however, in Rapid Accelerator Mode, code is also generated for the solver. In either case there will be some overhead due to communication between the generated code and Simulink (though in general that overhead would be greater in non-rapid accelerator mode).</p> <p>Now, whether you are going to see significant differences between these acceleration modes and full-on code generation will most likely depend on how you would be using the generated code. You had stated that your application is intended to essentially analyze/visualize the outputs of simulink models. Do you intend for you application, itself, to be a Simulink model? If so, I imagine your workflow would be that you generate code for the "plug-in" model and then incorporate this into your "parent" model as an s-function. Based on the descriptions given above, my gut feeling is that you would not see much of a performance improvement compared to accelerator mode.</p> <p>However, if your application is to be implemented outside of Simulink, then code generation would definitely be the way to go. In this case, you've completely eliminated the overhead of communicating with Simulink. In this workflow, you could, for example, generate a stand-alone executable from the "plug-in" model, execute that model to get the outputs, and then simply load those outputs for analysis and visualization into your application. Your application could be written in any language you want. In fact, you could even still write your application in MATLAB -- the key point, though, being that your application runs once the stand-alone executable (generated from the "plug-in" model) has <em>finished</em> executing, rather than interfacing with the plug-in model <em>while</em> it is executing.</p>
    singulars
    1. This table or related slice is empty.
    1. POPerformance improvement of simulink coder over accelerated models
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USgrungetta
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPerformance improvement of simulink coder over accelerated models
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYup, that pretty much sums it up! Another useful link to compare performance of the different simulation modes: http://www.mathworks.com/help/simulink/ug/comparing-performance.html
      singulars
      1. PO
      1. USpmb
    2. COI've come across these links/manuals as well. Unfortunately, the "Comparing Performance"-plot does not include a "Simulink Coder" line which was, what I was originally trying to find. The fact that both accelerator-modes already produce compiled models to some degree, led me to the question whether the Code-Generation would improve things performance-wise. Meanwhile, I'm doubting this... It's clear though, that performance is not the "declared" goal of the code-generation toolbox anway.
      singulars
      1. PO
      1. USsebastian
    3. COI generally agree. The main purpose of Simulink Coder is to allow generation of standalone code, and to a great extent, the speed improvement aspect of code generation is already available without Simulink Coder. Something else to consider -- rather than shelling out for Simulink Coder, maybe you'd be better off looking into the parallel computing tools for matlab/simulink. Your description of your usecase sounds sort of like a Monte Carlo approach. If the thousands of simulations you plan to run could be parallelized, that would offer a significant speed-up.
      singulars
      1. PO
      1. USgrungetta
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload