14:32 <TonyLo> Hi, I ran into an issue a couple of days ago that I have not been able to find a rsolution for. When running a Pony app on a Windows server blade cluster, pony only uses one of the NUMA nodes (on a high processor core blade, in this case dual socket 22 core (88 threads per blade)), setting --ponythtreads to 88 does not change the situation. I ran into a similar issue in the past with the JVM

14:32 <TonyLo> having a similar limitation. Anyone aware of a workaround for Pony?

15:30 <TwoNotes> Is there some Windows parameter that limits the number of CPUs a program can use?

15:32 <TonyLo> in .net apps you can set the config file to use all available cores, but nothing at the OS level

15:35 <TwoNotes> Perhaps per account, or per program invocation?

15:36 <TonyLo> I'm pretty sure it's a compiler level issue - I have .net apps that run fine on all cores

15:37 <TonyLo> This is the .net config setting: <Thread_UseAllCpuGroups enabled="true"/>

15:39 <TonyLo> .

15:54 <TonyLo> To add a little more info: processor groups are created when more than 64 logical processors exist on a machine, below this number there is not an issue, in my case I have 88 logical processors which means there are multiple cpu groups on each server. Only one group is being used by Pony.

16:00 <TwoNotes> So your pony program *is* using 64 processors?

16:09 <TwoNotes> Do NUMA nodes share memory? A single pony program has to have a single address space