Hi Chang Seok,
I understand that you intend to parallelize your MATLAB code to enhance its performance, particularly by utilizing the `parfor` loop for iterating over one of the state variables in your nested loop structure. However, you've observed that the execution does not seem to be parallelized effectively, as indicated by the sequential display of loop iterations and a lack of noticeable speed improvement.
1. Parallel Pool
Ensure that a parallel pool is active before executing the `parfor` loop. If a parallel pool is not already open, MATLAB will attempt to open one, which can add overhead, especially if the loop is relatively short. You can manually start a parallel pool using `parpool`
2. Overhead vs. Computation Time
The effectiveness of parallelization is more pronounced for loops where each iteration takes a significant amount of time. If the computations within each iteration are relatively quick, the overhead of distributing tasks among workers can outweigh the benefits. Your nested `fmincon` optimizations seem computationally intensive, which should, in theory, benefit from parallelization.
3. Data Transfer and Dependencies
`parfor` loops work best when each iteration is independent of others, minimizing the need for data transfer between workers. Your code appears to follow this principle, as each iteration writes to unique indices of `Vnew`, `indpol_ap`, `indpol_dp`, and `indadj`. However, ensure that all variables used within the loop are properly initialized and that there are no hidden dependencies.
4. Profiling and Optimization
Consider using MATLAB's Profiler to identify bottlenecks in your code. The Profiler can help you understand where the most time is spent and guide optimization efforts:
profile on
% Your code here
profile off
profile viewer
If after these considerations, you still do not observe improved performance, it might be worth examining more closely the specific computations within the loop or consulting MATLAB's parallel computing documentation for more advanced techniques, such as chunking iterations or optimizing data transfer between workers.
Hope this helps.
Regards,
Nipun
