How to speed up developed console application (.exe) from MCR (MATLAB R2012a)

I have compiled a console application (.exe) using MCR (MATLAB R2012a) which i want to run first on deployed system.

I am successfully getting executed result after double clicked on.exe file but getting double clicked,prompt windows is taking more than 50 sec to open and then prompting for inputs.

I am not aware of the cause of problem.i want to speed up my console applications (.exe) file so that it will take time to execute as short as possible.

Answer 1

[Walter Roberson]

The time to start up a MATLAB Compiler generated .exe will be fairly close to the time that would be required to start up MATLAB itself. What gets generated is akin to what you would get if you were to pcode your .m files and then hide the MATLAB command line.

[Dharmendra]

I am sorry to say you that i didn't get you completely. could you please elaborate further?

[Walter Roberson]

The MATLAB Compiler product does not compile in the same sense as a C compiler: it does not convert your MATLAB source code into native machine language code for the system it is running on.

Instead, the MATLAB Compiler converts the .m code into internal data structures that represent the code, using essentially the same process that interactive MATLAB uses for its JIT (Just In Time compiling). The data structures produced are written to data files. Then, the MATLAB Compiler adds on a chunk of software that knows how to interpret those ("threaded interpreted") data structures, and it is that chunk of software that forms the .exe .

The result is much the same as running MATLAB locked to a particular .m file, and without the command line to accept new commands -- because any program that knows how to run the data structures produced by its JIT effectively is MATLAB.