Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

jit options, cache and parallel #846

Closed
bmcfee opened this issue Mar 11, 2019 · 0 comments · Fixed by #855
Closed

jit options, cache and parallel #846

bmcfee opened this issue Mar 11, 2019 · 0 comments · Fixed by #855
Assignees
@bmcfee
Labels
management Project governance, packaging, distribution, etc
Milestone
0.7.0

Comments

@bmcfee
Copy link
Member

bmcfee commented Mar 11, 2019

Description

Currently, all numba jit operations are called with nopython=True, but we don't make use of any of the other flags. The following come to mind:

  • cache: store jit-compiled functions across sessions; we should definitely do this
  • parallel: use parallel optimizations. This may or may not make sense, and depends on the specific function in question.

We should do an audit of all numba functions used here, add caching, and check if parallelism helps.
@bmcfee bmcfee added the management Project governance, packaging, distribution, etc label Mar 11, 2019
@bmcfee bmcfee added this to the 0.7.0 milestone Mar 11, 2019
@bmcfee bmcfee self-assigned this Mar 11, 2019
bmcfee added a commit that referenced this issue Mar 23, 2019
@bmcfee
enabled jit caching for numba functions. fixes #846
5b286b7
@bmcfee bmcfee mentioned this issue Mar 23, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bmcfee bmcfee

Labels
management Project governance, packaging, distribution, etc
Milestone
0.7.0
Development

Successfully merging a pull request may close this issue.

JIT caching for numba functions librosa/librosa
1 participant
@bmcfee