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.

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

Extending semantics of BLOSC_NTHREADS and default value #185

Open
werner17 opened this issue Feb 3, 2017 · 0 comments
Open

Extending semantics of BLOSC_NTHREADS and default value #185

werner17 opened this issue Feb 3, 2017 · 0 comments

Comments

@werner17
Copy link

werner17 commented Feb 3, 2017

Some suggestions for the BLOSC_NTHREADS environment variable: It could be useful to have a zero or negative value to mean the number of cpu's not to use. So a value of 0 would mean to use all available CPU's, a value of -1 would mean to leave off one processor etc.

Currently its a bit workarounding that an application needs to find the number of threads itself and set it as environment variable, and it needs to do so before any BLOSC code might be possibly invoked. The default should be 0 then instead of 1, to use all available power . Currently it requires setting the environment variable to enable multithreading at all, but for a binary that you just give someone, that's too technical for all users (particularly windows-click-users).

A further option could also be support for values like BLOSC_NTHREADS=50% to always mean using half of the available CPU's only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant