Ah yea it seems like a NUMA issue.
If you go to the Debugging rollout of a tyFlow object, there is a "Print NUMA Info" button you can press, that will print all detected CPU info to the MAXScript listener. See if that reports 64 detected CPUs or not...
If it prints out 64 CPUs detected, then it looks like it's a windows thread scheduling issue. I create threads for each CPU on a machine, and assign (up to) that many simultaneous tasks, however windows does the actual scheduling itself.
It's possible that if windows is throttling CPUs like that, that you'll get worse performance in tyFlow because of it (ie, because tyFlow may create 64 threads, but they're spread across only 32 cores). Try loading up a really slow simulation that uses all 32 cores, and in the tyFlow main settings set max threads to 32 and see if it runs any faster....
Also check the CPU affinity of 3dsmax.exe in the windows task manager and make sure it's assigned to all 64 cores.
If you go to the Debugging rollout of a tyFlow object, there is a "Print NUMA Info" button you can press, that will print all detected CPU info to the MAXScript listener. See if that reports 64 detected CPUs or not...
If it prints out 64 CPUs detected, then it looks like it's a windows thread scheduling issue. I create threads for each CPU on a machine, and assign (up to) that many simultaneous tasks, however windows does the actual scheduling itself.
It's possible that if windows is throttling CPUs like that, that you'll get worse performance in tyFlow because of it (ie, because tyFlow may create 64 threads, but they're spread across only 32 cores). Try loading up a really slow simulation that uses all 32 cores, and in the tyFlow main settings set max threads to 32 and see if it runs any faster....
Also check the CPU affinity of 3dsmax.exe in the windows task manager and make sure it's assigned to all 64 cores.