[Numpy-discussion] Changing FFT cache to a bounded LRU cache

David Cournapeau cournape at gmail.com
Wed Jun 1 19:47:07 EDT 2016


On Tue, May 31, 2016 at 10:36 PM, Sturla Molden <sturla.molden at gmail.com>
wrote:

> Joseph Martinot-Lagarde <contrebasse at gmail.com> wrote:
>
> > The problem with FFTW is that its license is more restrictive (GPL), and
> > because of this may not be suitable everywhere numpy.fft is.
>
> A lot of us use NumPy linked with MKL or Accelerate, both of which have
> some really nifty FFTs. And the license issue is hardly any worse than
> linking with them for BLAS and LAPACK, which we do anyway. We could extend
> numpy.fft to use MKL or Accelerate when they are available.
>

That's what we used to do in scipy, but it was a PITA to maintain. Contrary
to blas/lapack, fft does not have a standard API, hence exposing a
consistent API in python, including data layout involved quite a bit of
work.

It is better to expose those through 3rd party APIs.

David


> Sturla
>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20160602/46d49426/attachment.html>


More information about the NumPy-Discussion mailing list