Set number of OpenBLAS threads #1414
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, just has some other thoughts. why the openblas threads has to be set to 1, wouldn't it be faster if there are more threads in computing with openblas? |
|
Hi @dyustc, I dunno but iirc it was eating the CPU and absolutely chugging when I was using a system package of openblas without this. |
|
Most of the time system is doing search actually, not using openblas at all. So openblas threads likely have no effect. If you are looking for efficient multicore recognizer, check recent neural network systems like sherpa. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This sets the number of openblas threads in case openblas wasn't compiled with
USE_LOCKING=1 USE_THREAD=0.This slightly nicer version is untested, but simply adding the #include and
openblas_set_num_threads(1);is what I patched for Alpine.