8000 np.convolve running on max threads with numpy >= 1.14.6 · Issue #13888 · numpy/numpy · GitHub
[go: up one dir, main page]
Skip to content

np.convolve running on max threads with numpy >= 1.14.6 #13888

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
Closed
aaronpearlman opened this issue Jul 2, 2019 · 2 comments
Closed

np.convolve running on max threads with numpy >= 1.14.6 #13888

aaronpearlman opened this issue Jul 2, 2019 · 2 comments

Comments

@aaronpearlman
Copy link

I am finding that running numpy.convolve with versions >= 1.14.6 automatically launches the job on all available CPUs/threads. Is this bug? This is not the behavior for numpy <= 1.14.5.

Reproducing code example:

import numpy as np
movingAvg = np.convolve(data, window, "same")

Numpy/Python version information:

('1.14.6', '2.7.12 (default, Nov 12 2018, 14:36:49) \n[GCC 5.4.0 20160609]')
@mattip
Copy link
Member
mattip commented Jul 2, 2019

Kind of a duplicate of #11826.

convolve calls correlate which uses dot underneath to do the heavy lifting for large arrays. By default this will use a thread for each CPU. You may be interested in the joblib/threadpoolctl package which allows you to control this.

@mattip
Copy link
Member
mattip commented Sep 12, 2019

Closing, the issue was asking for information which was provided. Please reopen if there is action to be taken.

Uh oh!

There was an error while loading. Please reload this page.
@mattip mattip closed this as completed Sep 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mattip @aaronpearlman
0