-
Notifications
You must be signed in to change notification settings - Fork 476
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
evaluate NUMA memory binding #110
Comments
@fireice-uk Could you please post the hwloc output |
Not sure if the ascii art will get garbled. |
Could you please try to use the newest version of xmr-stak with hwloc? It looks like core 0 and 2 are the physicle cores in your system( not 0,1). The new code with the function to overload a system if 1MiB for a hash is avalable should also suggest to use core 0 and 2. This should remove the fluctuations in the hashrate. I also used always core 0,1 until hwloc shows that 0,2 are the physical cores. |
I will give it a spin, and yes, seems you are correct on that point, we will need to properly allocate core affinity it seems:
|
@fireice-uk information: I am currently working on this issue. I have finished a prototype where the memory for a thread should be pinned to the numa node. |
Ok. Great, what's the setup you are testing on? |
Based on the discussion in #108 it could be useful to evaluate if there is any improvemnt if we can bind memory to the correct NUMA node.
@fireice-uk's observation
The text was updated successfully, but these errors were encountered: