-
Notifications
You must be signed in to change notification settings - Fork 23
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
Allow dcurl to affect the thread pool size of libtuv #149
Comments
You might learn from xmrig by searching |
I would like to add a new function in the src/threadpool.c of |
Continue from the last comment.
The function which is called first is important. If we continue this way, it might have some concern. |
In the initialization phase of dcurl, the threadpool size is preset to the (maximum processor - 1). Then the threadpool would be initialized in the first call of dcurl_entry(). Close DLTcollab#149.
In the initialization phase of dcurl, the threadpool size is preset to the (maximum processor - 1) with the new libtuv API uv_set_threadpool_size(). Then the threadpool would be initialized in the first call of dcurl_entry() with the preset size. Close DLTcollab#149.
I create a new API The size presetting happens in Since we assign the thread number to be used for PoW when calling the |
There are two methods to set the thread pool size of
libtuv
:libtuv
source code.UV_THREADPOOL_SIZE
to overwrite the default size.Based on the previous advice of method 1 pull request:
Objective:
Offer other acceptable methods to set the thread pool size and apply it to the current design.
The text was updated successfully, but these errors were encountered: