why MATLAB 2019b MEX file is slower

3 views (last 30 days)
Kat Lee
Kat Lee on 24 Oct 2019
Edited: James Tursa on 29 Oct 2019
Hey all
I am testing performance comparison among R2017b and R2019b, and I have noticed that for most .m functions, it's becoming way much faster, but one noticable thing is that the time for mex file (calling multi-thread C) has been tripled, which is very werid.
I believe this could be caused by some overhead in C or mex side. But am still very curious why a better MATLAB can cause slow down

Accepted Answer

James Tursa
James Tursa on 24 Oct 2019
Edited: James Tursa on 24 Oct 2019
Impossible to say for sure without knowing what your mex function is doing. One thing to note is that in R2018a the storage format of complex variables changed from separate real & imag to interleaved real & imag. So passing complex variables may force a copy-in-copy-out behavior in one version but not the other. What is your mex function doing?
James Tursa
James Tursa on 29 Oct 2019
If you are passing complex matrices back & forth, you absolutely need to rewrite your code for interleaved real & imag and compile with the -R2018a flag in order to regain that performance. If you need help with this don't hesitate to post more questions.
There are two ways to get at your data. Using the new data types as shown in the doc:
mxComplexDouble *xc = mxGetComplexDoubles(prhs[0]);
// then use xc[i].real and xc[i].imag in your code
Or using a regular primitive data type and adjusting the indexing by 2:
double *pr = (double *) mxGetData(prhs[0]);
// then use pr[i*2] and pr[i*2+1] for the real & imag parts in your code

Sign in to comment.

More Answers (0)


Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by