-
Notifications
You must be signed in to change notification settings - Fork 13
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.
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
control/query thread limit #66
Comments
It uses OpenMP so you can set the |
SpikeDetekt will use a different mechanism: you'll use IPython.parallel to set up the engines, either on the same computer, or on different computers. It should also work with cloud architectures like Spark. |
Some hybrid of both will probably occur for KK2. I think the plan is to support the current shared-memory multithreading as well as distributed memory multiprocessing through As for the ideal optimum number of cores to use: this probably depends on the size of your dataset; we'd welcome feedback on what you've found works best for you! |
This is probably my mistake, but I'm not having luck with the
Which isn't successful in limiting phy to one thread. |
HI, Not your fault: KK2 ignores the OMP_NUM_THREADS argument. I have fixed Dan On 17/07/2015 20:32, ereming wrote:
|
Hi, apologies if this is already addressed elsewhere. I'm running phy/kk2 on a SLURM computing cluster. I'd like to be able to know how many cores kk2 (and in the future, SpikeDetekt2) will be using so that I can make the appropriate resource request. Is that possible? Is it adjustable?
The text was updated successfully, but these errors were encountered: