I think this is an issue reported by other user, see
The problem can be reproduced by calling cplexlp within a for-loop or parfor loop.
1. using for loop, the memory consumed by MATLAB continuously increases.
2. using parfor loop, memory of each worker of MATLAB continuously increases.
3. using linprog instead of cplexlp, no such memory leak.
I cleared all unnecessary data at the end of each loop.
Any advice will be greatly appreciated!
Pinned topic Memory leak in Matlab interface
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-01-08T23:47:08Z at 2013-01-08T23:47:08Z by SystemAdmin
Re: Memory leak in Matlab interface2012-09-25T06:21:09ZThis is the accepted answer. This is the accepted answer.I also tried to use the cplex class object instead of cplexlp function. If I reuse the object as much as possible in the for-loop, the memory usage looks fine. But when using parfor-loop, I have to create the objects within each loop since MATLAB think this object can't be sliced. The memory increases a lot in the parfor case.
For the performance, using class object seems to be much slower than calling cplexlp in each case. Could someone please explain this difference?
I hope some one can help me with the memory issue. Right now, I have to restart MATLAB after a while, it's really annoying.....
RWunderling 270002THM1116 Posts
Re: Memory leak in Matlab interface2012-10-16T10:00:41ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
In the mean time, I understand you are in direct contact with the CPLEX dev team
for working on a workaround.
Re: Memory leak in Matlab interface2013-01-08T23:47:08ZThis is the accepted answer. This is the accepted answer.
- RWunderling 270002THM1