To check performance, I usually look at the generated machine code (`code_native`). If there's a type instability, the code is a mess. I understand that that's not everybody's preferred method since it requires reading and understanding machine code...
A better method would be to use `@time` and `@profile` in the usual manner. Inefficiencies and type instabilities should show up there. -erik On Fri, Feb 19, 2016 at 6:23 PM, Davide Lasagna <[email protected]> wrote: > Cool trick, thanks. I had a similar problem and ended up defining methods > with the Val{} argument for dispatch on different values. I was not entirely > happy with it, though, because of all the extra typing of parenthesis. Will > try adding an inlined calling method. > > How in practice would you go checking that you do not really hit performance? > > Davide -- Erik Schnetter <[email protected]> http://www.perimeterinstitute.ca/personal/eschnetter/
