When you launch your MATLAB executable, which relies on the MATLAB Compiler Runtime (MCR), from Visual Studio, a significant portion of the delay comes from initializing the runtime environment. This overhead is inherent to how MATLAB-compiled applications start up, so if you call the EXE repeatedly, you incur this startup cost every time.
The suggestions can be quite generic but, instead of launching a new MATLAB EXE for every call, try designing your application so that the MCR is started only once. Additionally, if your code does not require Java features, you might consider launching it with options such as "-nojvm" to reduce startup time.
Karan
