How to avoid repeatly loading parallel pool when running .exe matlab file in cmd
4 次查看(过去 30 天)
显示 更早的评论
I am using parfor in a matlab program.
Then I generate a excutable .exe file using "mcc -m " command on that program.
Later, when we I call the .exe file in cmd, the program load parallel pool everytime:
"Starting parallel pool (parpool) using the 'Processes' profile ..."
It takes so much time since I need to repeatly call it.
Do you know any way to avoid loading parpool every time when I call it? Can I preload it in cmd? Thank you.
8 个评论
Damian Pietrus
2024-10-16
As long as the code ran as expected on your local machine, you should be able to have it run separately on your colleague's machines as well. A thread pool is limited to one physical machine at a time, meaning that both you and your colleagues can separately run the code on your own systems. Where a thread pool would not be supported would be taking one instance of your application and having the pool open across multiple machines.
采纳的回答
Damian Pietrus
2024-10-16
Moving from comments to an Answer:
When a processes parpool is launched, multiple separate MATLAB processes are initiated. The client then connects to these separate processes and the pool is established. Since each instance of your .exe is a separate client, you will always end up opening a pool every time you launch the file.
If the pool startup time is your main issue, there is one potential option. If the code in your parfor is thread safe, you can launch a thread pool instead of a process pool. Here, the workers run as a thread in the main MATLAB processes and share memory, with the added benefit of quicker startup. There's some more info here:
Note that while thread workers are supported in standalone applications created using Compiler, not all functions are supported in a thread pool. Also note that a single instance of your application can only run on your local machine -- a threadpool cannot be opened across multiple compute nodes
0 个评论
更多回答(2 个)
Hitesh
2024-10-16
The issue might occur if the code is creating new “parpool” everytime without checking the existence of the existing “parpool”. To avoid creating new “parpool” and use the existing instance you need to check the existence of existing parpool. You can add the below condition to check for any active "parpool" before calling "parfor". Kindly refer to the below code for an example:
if isempty(gcp('nocreate'))
parpool('Processes');
end
Please find below the description of the functions used in above code example.
- gcp('nocreate'): This command checks if a parallel pool is currently active. The "nocreate" option ensures that it only checks for an existing pool and does not create a new one if none exists.
- isempty(...): This function checks if the result of "gcp('nocreate')" is empty, meaning no parallel pool is currently running.
- parpool('Processes'): If no parallel pool is found, this line starts a new parallel pool using the 'Processes' profile.
For more information on "parpool" and "gcp('nocreate')", refer to the below MATLAB Documentation:
Walter Roberson
2024-10-16
The official way to reduce the initiation time is to use the MATLAB Production Server product; it keeps pools "warm" so there is little time spent initializing pools.
If you do not use MATLAB Production Server, then there is no solution to your difficulty.
另请参阅
类别
在 Help Center 和 File Exchange 中查找有关 Parallel Computing Fundamentals 的更多信息
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!