WuProp build finished

[Bryan]

The 64th thread is what matters. Go past that and Numa kicks in

Well I'm sure glad I didn't build one of the new 44C/88T machines. Besides having to hock my soul to pay for it I would have really been PO'd when I couldn't use all of those suckers

@Z, I used 8x16G memory sticks so there is 1 per memory channel.

Since JPM weighed in then that is the definitive answer. I won't argue with that boy

[zombie67]

The 64th thread is what mattwrs. Go past that and Numa kicks in

Okay. But what does that mean exactly? You need to configure DIMMs differently? Run dual VMs of windows somehow? I read the wiki about NUMA, but it really doesn't explain the part about how you implement it, or work around it, or turn it off.

[zombie67]

NUMA is not limited to Windows.

http://man7.org/linux/man-pages/man7/numa.7.html

[John P. Myers]

When NUMA kicks in, it assigns groups of 64 threads to a node (by default). You can have more than 1 node going, but the way it works is that a program that launches another program can only launch that other program into the same node it resides in, meaning BOINC cannot use more than 1 node. It can see all threads over 64, but can't assign WUs to them.

If using Windows, a VM would be the way to go. Or you could turn HT off. Or figure out how to run 2 instances of BOINC at the same time, assigning 1 to node 1 while the default remains in node 0. Or beg the BOINC devs to code for more than 1 node.

Or just use Linux