You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 18, 2020. It is now read-only.
The data_thread_num is hardcoded in config file, and I think we could make this value is related to number of CPU's on the machine. For example, set data_thread_num to std::hardwared_concurrency()*0.75
The text was updated successfully, but these errors were encountered:
since hardware_concurrency just is hint of the system's concurrency thread number. And there is still many argues between the number of thread and the number of cpu cores. In my opinion, I would like to set the thread number equal to ther core-number * 1.5. There is a discussion to tell us why we should set thread number more than core number. Then main idea is that the disk IO operation may block the thread. when cpu run schedule() function, it's better to have another thread to run. I have forgot this article...
The
data_thread_num
is hardcoded in config file, and I think we could make this value is related to number of CPU's on the machine. For example, setdata_thread_num
to std::hardwared_concurrency()*0.75The text was updated successfully, but these errors were encountered: