- put your parts of the algorithm into different .c files
- write a mex interface for each of them for running your unit tests
- have an overall mex file calling those subfunctions (and pass all the .c files to mex for compilation.
Overhead of calling MEX functions from another MEX file
3 visualizaciones (últimos 30 días)
Mostrar comentarios más antiguos
I have an algorithm implemented in Matlab. It consists of many functions, each function in separate file and having its own unit tests made in xUnit. The algorithm is rather simple, but it is heavily based on bit operations, which makes it extremely slow in Matlab. I decided that I will reimplement it in C using MEX files. Now I'm facing two choices:
1. Create only one MEX file acting as an interface to the whole algorithm and implement all the functions as ordinary C functions.
2. Reimplement each function as a separate MEX file.
The first approach seems better in terms of performance, but it forces me to drop all the unit tests and I'm reluctant to do that since I'm new to MEX files and I still make some mistakes. The second approach allows me to unit-test every MEX function, but it will result in MEX functions calling other MEX functions. I'm afraid that this might impact performance, and after all performance is what I'm after. Should I be worried with the overhead of calling MEX from MEX?
0 comentarios
Respuesta aceptada
Titus Edelhofer
el 21 de Dic. de 2011
Hi Jan,
what about doing both? Having the overall algorithm spread over many mex files probably is no good idea since you will indeed see quite some overhead. But what you could do is:
Titus
2 comentarios
Titus Edelhofer
el 25 de Dic. de 2011
Yes. Although there is no reason not to seperate e.g. the test files into a different folder ....
Más respuestas (0)
Ver también
Categorías
Más información sobre Write C Functions Callable from MATLAB (MEX Files) en Help Center y File Exchange.
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!