Permute(., ) %// interchange dims 2 and 4: we have dims
For example, permute(x, ) is equivalent to this sequence of elementary permute operations (the sequence is not unique): permute(., ) %// interchange dims 1 and 4: we have dims Permuting of dimensions can always be done as a sequence of elementary permute operations, where" elementary" means interchanging only two dimensions. This is only a guess, as I don't really know what permute does under the hood. While this is not exactly the best way to profile memory usage (better use a proper memory profiler, something like Intel Inspector XE), it does show to some degree that permute is indeed not working in-place. You can see how at its peak the function reached twice as much memory usage as when it returned. I also repeated the test under perfmon.exe which showed the same pattern: I then ran the function simply as: %clear aĪnd watched the memory usage It went from 1.8 gigs in use, and rose to 5.2 then quickly down to 3.6 gigs. I only have 8 gigs of RAM on my laptop, so to avoid thrashing I modified your function as: function out = mtest()
I also set the "update speed" to "high" to get a finer time resolution.
#Matlabe permute windows#
In Windows 10, I opened the "task manager" on the "performance" tab with the "memory" graphs in view. The permute method in fact does create a second copy of the matrix with the data permuted and returns it. Your argument is flawed because the MATLAB memory profiler is not telling you the truth!
0 kommentar(er)
