As per the support case 2568917, configuring processor affinity for WP/AS is only supported on machines with a maximum of 64 logical processors.
<performance>
<!-- Configuration related to containers.
The runningInside flag is used to enable various optimizations that can be done when running inside a container.
For example it's assumed that only one service instance is running and that there are no other processes except standard windows stuff. -->
<container runningInside="false"/>
<!-- Configuration related to processor.
affinity flag is used to set processor affinity. Empty string or "0" is interpreted as "all processors" -->
<processor affinity="00001111" />
The support team noted:
>As of now, Spotfire does not handle a 128-bit number for the Affinity setting.
The native Process.ProcessorAffinity property in .NET uses a single pointer-sized bitmask (IntPtr), which restricts its capacity to a maximum of 64 logical processors on a 64-bit operating system.
Thank you for sharing your use case. We have internally reported your case for further improvement.
Therefore, we would like to use this Enhancement Request (ER) as a reference for our follow-up.