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

Use cache=True on everything? #66

Open
NicolasHug opened this issue Dec 11, 2018 · 3 comments
Open

Use cache=True on everything? #66

NicolasHug opened this issue Dec 11, 2018 · 3 comments
Labels
perf Computational performance issue or improvement

Comments

@NicolasHug
Copy link
Collaborator

Opened numba/numba#3588 to ask if there's an alternative.
@NicolasHug
Copy link
Collaborator Author

There's none (for now).

Do we want to cache all compilations @ogrisel ? I'd say yes, since it takes a non-negligible amount of time

@NicolasHug
Copy link
Collaborator Author

NicolasHug commented Dec 13, 2018 •
edited
Loading

So I did that, cache=True is not supported for jitclasses nor when parallel=True so gain is pretty minimal: going from about 10s to 9s.

@ogrisel
Copy link
Owner

ogrisel commented Dec 13, 2018

Ok so better wait for a better caching infrastructure in numba before enabling it.

@ogrisel ogrisel added the perf Computational performance issue or improvement label Dec 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
perf Computational performance issue or improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ogrisel @NicolasHug