
May 30, 2016
4:07 a.m.
Marten van Kerkwijk <m.h.vankerkwijk <at> gmail.com> writes:
I did a few simple timing tests (see comment in PR), which suggests it is hardly worth having the cache. Indeed, if one really worries about speed, one should probably use pyFFTW (scipy.fft is a bit faster too, but at least for me the way real FFT values are stored is just too inconvenient). So, my suggestion would be to do away with the cache altogether.
The problem with FFTW is that its license is more restrictive (GPL), and because of this may not be suitable everywhere numpy.fft is.